[
https://issues.apache.org/jira/browse/HIVE-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029608#comment-13029608
]
Ashutosh Chauhan commented on HIVE-2029:
----------------------------------------
Thinking more about it, I think retrial is a responsibility of ORM layer
(jdo/datanucleus) not of application (Metastore in this case). Datanucleus
already provides this failover facility:
http://www.datanucleus.org/products/accessplatform_3_0/rdbms/failover.html
Looks like I am missing something here. Why retrials are implemented in
Metastore and we don't make use of datanucleus feature here?
> MetaStore ConnectionURL updates need to trigger creation of Default DB if it
> doesn't exist
> ------------------------------------------------------------------------------------------
>
> Key: HIVE-2029
> URL: https://issues.apache.org/jira/browse/HIVE-2029
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.7.0
> Reporter: Carl Steinbach
> Attachments: hive_2029.patch
>
>
> HIVE-1219 defined the JDOConnectionURLHook plugin, and integrated this
> feature into HiveMetaStore. On MetaStore operation failures, this plugin is
> used to update the metastore ConnectionURL configuration property. Currently
> this update triggers the reinitialization of the underlying JDO
> PersistenceManager, but it does not trigger checks to see if the default
> database exists, nor will it create the default database if it does not
> exist. It needs to do both.
> This ticket also covers removing the 'hive.metastore.force.reload.conf'
> property from HiveConf and HiveMetaStore. This property should not have been
> added in the first place since its sole purpose is to facilitate testing of
> the JDOConnectionURLHook mechanism by unnaturally forcing reinitialization of
> the PersistenceManager.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
