hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naveen Gangam (JIRA)" <>
Subject [jira] [Updated] (HIVE-11072) Add data validation between Hive metastore upgrades tests
Date Tue, 21 Jul 2015 03:12:04 GMT


Naveen Gangam updated HIVE-11072:
    Attachment: HIVE-11072.3.patch

This version of the patch addresses an issue with postgres where the case of the table names
causes it to not match the table when inserting the data into the table. The "hive-txn-schema-0.13.0.postgres.sql"
contains create statements like

where are the other schema files contains definitions
  "VER_ID" bigint,
  "SCHEMA_VERSION" character varying(127) NOT NULL,
  "VERSION_COMMENT" character varying(255) NOT NULL

In the latter definition, all names are enclosed in double quotes that causes postgres to
use the case as-is (upper case) where as in the former the tables are created with lower-case
names and can only be found either using lower-case names or uppercase without the quotes.

In the latest patch, I preserve the quotes around these definitions while parsing them and
use them as-is.

> Add data validation between Hive metastore upgrades tests
> ---------------------------------------------------------
>                 Key: HIVE-11072
>                 URL:
>             Project: Hive
>          Issue Type: Task
>          Components: Tests
>            Reporter: Sergio Peña
>            Assignee: Naveen Gangam
>         Attachments: HIVE-11072.1.patch, HIVE-11072.2.patch, HIVE-11072.3.patch
> An existing Hive metastore upgrade test is running on Hive jenkins. However, these scripts
do test only database schema upgrade, not data validation between upgrades.
> We should validate data between metastore version upgrades. Using data validation, we
may ensure that data won't be damaged, or corrupted when upgrading the Hive metastore.

This message was sent by Atlassian JIRA

View raw message