[
https://issues.apache.org/jira/browse/HIVE-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090537#comment-15090537
]
Lefty Leverenz commented on HIVE-1841:
--------------------------------------
Thanks Ashutosh. I removed the TODOC2.0 label.
But after this patch, HIVE-6113 removed datanucleus.fixedDatastore so I updated
the wiki again:
* [Configuration Properties -- datanucleus.fixedDatastore |
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-datanucleus.fixedDatastore]
> datanucleus.fixedDatastore should be true in hive-default.xml
> --------------------------------------------------------------
>
> Key: HIVE-1841
> URL: https://issues.apache.org/jira/browse/HIVE-1841
> Project: Hive
> Issue Type: Improvement
> Components: Configuration, Metastore
> Affects Versions: 0.6.0
> Reporter: Edward Capriolo
> Assignee: Ashutosh Chauhan
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HIVE-1841.1.patch.txt, HIVE-1841.2.patch, HIVE-1841.patch
>
>
> Two datanucleus variables:
> {noformat}
> <property>
> <name>datanucleus.autoCreateSchema</name>
> <value>false</value>
> </property>
> <property>
> <name>datanucleus.fixedDatastore</name>
> <value>true</value>
> </property>
> {noformat}
> are dangerous. We do want the schema to auto-create itself, but we do not
> want the schema to auto update itself.
> Someone might accidentally point a trunk at the wrong meta-store and
> unknowingly update. I believe we should set this to false and possibly trap
> exceptions stemming from hive wanting to do any update. This way someone has
> to actively acknowledge the update, by setting this to true and then starting
> up hive, or leaving it false, removing schema modifies for the user that hive
> usages, and doing all the time and doing the updates by hand.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
