hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <>
Subject [jira] [Commented] (HIVE-3764) Support metastore version consistency check
Date Mon, 03 Dec 2012 22:19:58 GMT


Ashutosh Chauhan commented on HIVE-3764:

I like the idea of this consistency check and having autoCreate turned off by default.
I havent looked at the patch in much detail, but hard-coding version number in the code is
not the great idea. Standard mechanism for this is to determine current version at compile
time via saveVersion scripts and then use that. HIVE-2926 is trying to add that in. Either
we should finish that one up or take the bits out from it of saveVersion and include in this
> Support metastore version consistency check
> -------------------------------------------
>                 Key: HIVE-3764
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>            Reporter: Prasad Mujumdar
>            Assignee: Prasad Mujumdar
>             Fix For: 0.10.0
>         Attachments: HIVE-3764-1.patch
> Today there's no version/compatibility information stored in hive metastore. Also the
datanucleus configuration property to automatically create missing tables is enabled by default.
If you happen to start an older or newer hive or don't run the correct upgrade scripts during
migration, the metastore would end up corrupted. The autoCreate schema is not always sufficient
to upgrade metastore when migrating to newer release. It's not supported with all databases.
Besides the migration often involves altering existing table, changing or moving data etc.
> Hence it's very useful to have some consistency check to make sure that hive is using
correct metastore and for production systems the schema is not automatically by running hive.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message