[ https://issues.apache.org/jira/browse/HIVE-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brock Noland updated HIVE-3764: ------------------------------- Attachment: HIVE-3764.4.patch Since the 0.13-additional-patch is only schema for 0.13, we want HIVE-3764.4.patch to run as part of the tests. The problem is that 0.13-additional-patch was uploaded later so that will be tested. Therefore I am reuploading your original patch HIVE-3764.4.patch. > Support metastore version consistency check > ------------------------------------------- > > Key: HIVE-3764 > URL: https://issues.apache.org/jira/browse/HIVE-3764 > 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, > 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: http://www.atlassian.com/software/jira