hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-1841) datanucleus.fixedDatastore should be true in hive-default.xml
Date Fri, 13 Nov 2015 19:33:11 GMT

     [ https://issues.apache.org/jira/browse/HIVE-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ashutosh Chauhan updated HIVE-1841:
-----------------------------------
    Attachment: HIVE-1841.2.patch

Fixed test failures.

>  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
>         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)

Mime
View raw message