hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HIVE-1841) datanucleus.fixedDatastore should be true in hive-default.xml
Date Tue, 18 Jan 2011 22:13:43 GMT

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

Edward Capriolo updated HIVE-1841:
----------------------------------

    Description: 
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. 


  was:

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. 


       Priority: Minor  (was: Major)

>  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
>            Priority: Minor
>             Fix For: 0.7.0
>
>         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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message