You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Carl Steinbach (JIRA)" <ji...@apache.org> on 2011/03/16 19:57:29 UTC
[jira] Created: (HIVE-2059) Add datanucleus.identifierFactory
property HiveConf to avoid unintentional MetaStore Schema corruption
Add datanucleus.identifierFactory property HiveConf to avoid unintentional MetaStore Schema corruption
------------------------------------------------------------------------------------------------------
Key: HIVE-2059
URL: https://issues.apache.org/jira/browse/HIVE-2059
Project: Hive
Issue Type: Bug
Components: Metastore
Affects Versions: 0.7.0
Reporter: Carl Steinbach
Assignee: Carl Steinbach
Fix For: 0.7.0
Attachments: HIVE-2059.1.patch.txt
Hive 0.6.0 we upgraded the version of DataNucleus from 1.0 to 2.0, which changed some of the defaults for how field names get mapped to datastore identifiers. This was problem was resolved in HIVE-1435 by setting datanucleus.identifierFactory=datanucleus in hive-default.xml
However, this property definition was not added to HiveConf. This can result in schema corruption if the user upgrades from Hive 0.5.0 to 0.6.0 or 0.7.0 and retains the Hive 0.5.0 version hive-default.xml on their classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HIVE-2059) Add datanucleus.identifierFactory
property HiveConf to avoid unintentional MetaStore Schema corruption
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-2059:
---------------------------------
Priority: Blocker (was: Major)
> Add datanucleus.identifierFactory property HiveConf to avoid unintentional MetaStore Schema corruption
> ------------------------------------------------------------------------------------------------------
>
> Key: HIVE-2059
> URL: https://issues.apache.org/jira/browse/HIVE-2059
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.7.0
> Reporter: Carl Steinbach
> Assignee: Carl Steinbach
> Priority: Blocker
> Fix For: 0.7.0
>
> Attachments: HIVE-2059.1.patch.txt
>
>
> Hive 0.6.0 we upgraded the version of DataNucleus from 1.0 to 2.0, which changed some of the defaults for how field names get mapped to datastore identifiers. This was problem was resolved in HIVE-1435 by setting datanucleus.identifierFactory=datanucleus in hive-default.xml
> However, this property definition was not added to HiveConf. This can result in schema corruption if the user upgrades from Hive 0.5.0 to 0.6.0 or 0.7.0 and retains the Hive 0.5.0 version hive-default.xml on their classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HIVE-2059) Add datanucleus.identifierFactory
property to HiveConf to avoid unintentional MetaStore Schema corruption
Posted by "John Sichi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Sichi updated HIVE-2059:
-----------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
Committed to branch and trunk. Thanks Carl!
> Add datanucleus.identifierFactory property to HiveConf to avoid unintentional MetaStore Schema corruption
> ---------------------------------------------------------------------------------------------------------
>
> Key: HIVE-2059
> URL: https://issues.apache.org/jira/browse/HIVE-2059
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.7.0
> Reporter: Carl Steinbach
> Assignee: Carl Steinbach
> Priority: Blocker
> Fix For: 0.7.0
>
> Attachments: HIVE-2059.1.patch.txt
>
>
> Hive 0.6.0 we upgraded the version of DataNucleus from 1.0 to 2.0, which changed some of the defaults for how field names get mapped to datastore identifiers. This was problem was resolved in HIVE-1435 by setting datanucleus.identifierFactory=datanucleus in hive-default.xml
> However, this property definition was not added to HiveConf. This can result in schema corruption if the user upgrades from Hive 0.5.0 to 0.6.0 or 0.7.0 and retains the Hive 0.5.0 version hive-default.xml on their classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HIVE-2059) Add datanucleus.identifierFactory
property HiveConf to avoid unintentional MetaStore Schema corruption
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-2059:
---------------------------------
Status: Patch Available (was: Open)
> Add datanucleus.identifierFactory property HiveConf to avoid unintentional MetaStore Schema corruption
> ------------------------------------------------------------------------------------------------------
>
> Key: HIVE-2059
> URL: https://issues.apache.org/jira/browse/HIVE-2059
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.7.0
> Reporter: Carl Steinbach
> Assignee: Carl Steinbach
> Fix For: 0.7.0
>
> Attachments: HIVE-2059.1.patch.txt
>
>
> Hive 0.6.0 we upgraded the version of DataNucleus from 1.0 to 2.0, which changed some of the defaults for how field names get mapped to datastore identifiers. This was problem was resolved in HIVE-1435 by setting datanucleus.identifierFactory=datanucleus in hive-default.xml
> However, this property definition was not added to HiveConf. This can result in schema corruption if the user upgrades from Hive 0.5.0 to 0.6.0 or 0.7.0 and retains the Hive 0.5.0 version hive-default.xml on their classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HIVE-2059) Add datanucleus.identifierFactory
property to HiveConf to avoid unintentional MetaStore Schema corruption
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-2059:
---------------------------------
Summary: Add datanucleus.identifierFactory property to HiveConf to avoid unintentional MetaStore Schema corruption (was: Add datanucleus.identifierFactory property HiveConf to avoid unintentional MetaStore Schema corruption)
> Add datanucleus.identifierFactory property to HiveConf to avoid unintentional MetaStore Schema corruption
> ---------------------------------------------------------------------------------------------------------
>
> Key: HIVE-2059
> URL: https://issues.apache.org/jira/browse/HIVE-2059
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.7.0
> Reporter: Carl Steinbach
> Assignee: Carl Steinbach
> Priority: Blocker
> Fix For: 0.7.0
>
> Attachments: HIVE-2059.1.patch.txt
>
>
> Hive 0.6.0 we upgraded the version of DataNucleus from 1.0 to 2.0, which changed some of the defaults for how field names get mapped to datastore identifiers. This was problem was resolved in HIVE-1435 by setting datanucleus.identifierFactory=datanucleus in hive-default.xml
> However, this property definition was not added to HiveConf. This can result in schema corruption if the user upgrades from Hive 0.5.0 to 0.6.0 or 0.7.0 and retains the Hive 0.5.0 version hive-default.xml on their classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HIVE-2059) Add datanucleus.identifierFactory
property HiveConf to avoid unintentional MetaStore Schema corruption
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-2059:
---------------------------------
Attachment: HIVE-2059.1.patch.txt
> Add datanucleus.identifierFactory property HiveConf to avoid unintentional MetaStore Schema corruption
> ------------------------------------------------------------------------------------------------------
>
> Key: HIVE-2059
> URL: https://issues.apache.org/jira/browse/HIVE-2059
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.7.0
> Reporter: Carl Steinbach
> Assignee: Carl Steinbach
> Fix For: 0.7.0
>
> Attachments: HIVE-2059.1.patch.txt
>
>
> Hive 0.6.0 we upgraded the version of DataNucleus from 1.0 to 2.0, which changed some of the defaults for how field names get mapped to datastore identifiers. This was problem was resolved in HIVE-1435 by setting datanucleus.identifierFactory=datanucleus in hive-default.xml
> However, this property definition was not added to HiveConf. This can result in schema corruption if the user upgrades from Hive 0.5.0 to 0.6.0 or 0.7.0 and retains the Hive 0.5.0 version hive-default.xml on their classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HIVE-2059) Add datanucleus.identifierFactory
property to HiveConf to avoid unintentional MetaStore Schema corruption
Posted by "John Sichi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007636#comment-13007636 ]
John Sichi commented on HIVE-2059:
----------------------------------
+1. Will commit when tests pass.
> Add datanucleus.identifierFactory property to HiveConf to avoid unintentional MetaStore Schema corruption
> ---------------------------------------------------------------------------------------------------------
>
> Key: HIVE-2059
> URL: https://issues.apache.org/jira/browse/HIVE-2059
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.7.0
> Reporter: Carl Steinbach
> Assignee: Carl Steinbach
> Priority: Blocker
> Fix For: 0.7.0
>
> Attachments: HIVE-2059.1.patch.txt
>
>
> Hive 0.6.0 we upgraded the version of DataNucleus from 1.0 to 2.0, which changed some of the defaults for how field names get mapped to datastore identifiers. This was problem was resolved in HIVE-1435 by setting datanucleus.identifierFactory=datanucleus in hive-default.xml
> However, this property definition was not added to HiveConf. This can result in schema corruption if the user upgrades from Hive 0.5.0 to 0.6.0 or 0.7.0 and retains the Hive 0.5.0 version hive-default.xml on their classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HIVE-2059) Add datanucleus.identifierFactory
property HiveConf to avoid unintentional MetaStore Schema corruption
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007631#comment-13007631 ]
Carl Steinbach commented on HIVE-2059:
--------------------------------------
Review request: https://reviews.apache.org/r/515/
> Add datanucleus.identifierFactory property HiveConf to avoid unintentional MetaStore Schema corruption
> ------------------------------------------------------------------------------------------------------
>
> Key: HIVE-2059
> URL: https://issues.apache.org/jira/browse/HIVE-2059
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.7.0
> Reporter: Carl Steinbach
> Assignee: Carl Steinbach
> Priority: Blocker
> Fix For: 0.7.0
>
> Attachments: HIVE-2059.1.patch.txt
>
>
> Hive 0.6.0 we upgraded the version of DataNucleus from 1.0 to 2.0, which changed some of the defaults for how field names get mapped to datastore identifiers. This was problem was resolved in HIVE-1435 by setting datanucleus.identifierFactory=datanucleus in hive-default.xml
> However, this property definition was not added to HiveConf. This can result in schema corruption if the user upgrades from Hive 0.5.0 to 0.6.0 or 0.7.0 and retains the Hive 0.5.0 version hive-default.xml on their classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira