[
https://issues.apache.org/jira/browse/HIVE-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002976#comment-15002976
]
Ashutosh Chauhan commented on HIVE-1841:
----------------------------------------
Now we have schemaTool which automates schema creation process. We can document
that as step in installation guide.
Given that Hive is now used in lot of production scenario and metasore being
used by components outside of Hive, we need to make defaults favor production
scenarios rather than for beginners.
> 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
> Priority: Minor
> Attachments: HIVE-1841.1.patch.txt
>
>
> 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)
