[
https://issues.apache.org/jira/browse/HIVE-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969566#action_12969566
]
Ning Zhang commented on HIVE-1841:
----------------------------------
Yeah, I think it is good to at least to include datanucleus.fixedDataStore in
hive-default.xml. I think it should also be OK to set the default value to
'true' if all the current unit tests pass. But as a rule-of-thumb, a
hive-site.xml is necessary for any Hive query running on production cluster.
Paul, do you see other potential problems by changing the default value of
datanucleus.fixedDataStore in hive-default.xml.
> 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
> Affects Versions: 0.6.0
> Reporter: Edward Capriolo
> Fix For: 0.7.0
>
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
