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

Lefty Leverenz commented on HIVE-12436:
---------------------------------------

Doc note:  This needs to be documented in Configuration Properties for release 
2.0.0.  Since the setting of *hive.metastore.schema.verification* affects 
*datanucleus.autoCreateSchema*, both parameters should be updated:

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

For *datanucleus.autoCreateSchema* the wiki currently says "Default Value: true 
unless hive.metastore.schema.verification is true" so I suggest adding "(Hive 
0.x and 1.x)" as well as "false unless hive.metastore.schema.verification is 
false (Hive 2.x)".

Additional revisions are needed here:

* [Admin Manual -- Metastore Admin -- Metastore Schema Consistency and Upgrades 
| 
https://cwiki.apache.org/confluence/display/Hive/AdminManual+MetastoreAdmin#AdminManualMetastoreAdmin-MetastoreSchemaConsistencyandUpgrades]
* [Hive Schema Tool -- Metastore Schema Verification | 
https://cwiki.apache.org/confluence/display/Hive/Hive+Schema+Tool#HiveSchemaTool-MetastoreSchemaVerification]

> Default hive.metastore.schema.verification to true
> --------------------------------------------------
>
>                 Key: HIVE-12436
>                 URL: https://issues.apache.org/jira/browse/HIVE-12436
>             Project: Hive
>          Issue Type: Task
>          Components: Metastore
>            Reporter: Ashutosh Chauhan
>            Assignee: Ashutosh Chauhan
>              Labels: TODOC2.0
>             Fix For: 2.0.0
>
>         Attachments: HIVE-12436.patch
>
>
> It enforces metastore schema version consistency



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to