[jira] [Updated] (HIVE-1841) datanucleus.fixedDatastore should be true in hive-default.xml

2011-04-05 Thread Carl Steinbach (JIRA) 

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

Carl Steinbach updated HIVE-1841:
-

Component/s: Metastore

>  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}
> 
>  datanucleus.autoCreateSchema
>  false
> 
> 
>  datanucleus.fixedDatastore
>  true
> 
> {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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (HIVE-1841) datanucleus.fixedDatastore should be true in hive-default.xml

2011-01-18 Thread Edward Capriolo (JIRA) 

 [ 
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}

 datanucleus.autoCreateSchema
 false



 datanucleus.fixedDatastore
 true

{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}

 datanucleus.autoCreateSchema
 false



 datanucleus.fixedDatastore
 true

{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}
> 
>  datanucleus.autoCreateSchema
>  false
> 
> 
>  datanucleus.fixedDatastore
>  true
> 
> {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.

[jira] Updated: (HIVE-1841) datanucleus.fixedDatastore should be true in hive-default.xml

2011-01-18 Thread Carl Steinbach (JIRA) 

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

Carl Steinbach updated HIVE-1841:
-

Attachment: HIVE-1841.1.patch.txt

This patch set datanucleus.fixedDatastore=true 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
>
> Attachments: HIVE-1841.1.patch.txt
>
>
> Two datanucleus variables:
> {noformat}
> 
>  datanucleus.autoCreateSchema
>  false
> 
> 
>  datanucleus.fixedDatastore
>  true
> 
> {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.