[ 
https://issues.apache.org/jira/browse/HIVE-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090494#comment-15090494
 ] 

Lefty Leverenz commented on HIVE-3764:
--------------------------------------

Doc note:  This adds two configuration parameters to HiveConf.java in 0.12.0.  
They're documented in the wiki here:

* [Configuration Properties -- datanucleus.fixedDatastore | 
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-datanucleus.fixedDatastore]
* [Configuration Properties -- hive.metastore.schema.verification | 
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-hive.metastore.schema.verification]

Their default values are changed in release 2.0.0 by HIVE-1841 and HIVE-12436, 
respectively.

> 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-12.3.patch, HIVE-3764-trunk.3.patch, 
> HIVE-3764.1.patch, HIVE-3764.2.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 was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to