[
https://issues.apache.org/jira/browse/HIVE-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad Mujumdar updated HIVE-3764:
----------------------------------
Fix Version/s: 0.10.0
Status: Patch Available (was: Open)
The metastore version is set the in code and a new table is created in
metastore to store it on the disk. The schema creation and upgrade scripts add
the version string to the metastore.
The version is verified while opening the metastore. A new property
hive.metastore.schema.verification (disabled by default) is added to enable
this verification. Setting this property also disables autoCreateSchema and
enables fixedDataStore for datanucleus.
> Support metastore version consistency check
> -------------------------------------------
>
> Key: HIVE-3764
> URL: https://issues.apache.org/jira/browse/HIVE-3764
> 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: http://www.atlassian.com/software/jira
