hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brock Noland (JIRA)" <>
Subject [jira] [Commented] (HIVE-3764) Support metastore version consistency check
Date Fri, 13 Sep 2013 13:36:54 GMT


Brock Noland commented on HIVE-3764:

[~thejas], I'd really like to get this into 0.12. I just had two people email me directly
yesterday and both were using the incorrect metastore version. I've also seen this issue dozens
of times in the past couple years. Additionally the patch looks quite good.
> Support metastore version consistency check
> -------------------------------------------
>                 Key: HIVE-3764
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>    Affects Versions: 0.8.0, 0.9.0, 0.10.0, 0.11.0
>            Reporter: Prasad Mujumdar
>            Assignee: Prasad Mujumdar
>             Fix For: 0.12.0
>         Attachments: HIVE-3764-0.13-addional-file.patch, HIVE-3764.4.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.
> Besides it would be helpful to add a tool that can leverage this version information
to figure out the required set of upgrade scripts, and execute those against the configured
metastore. Now that Hive includes Beeline client, it can be used to execute the scripts.

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