[
https://issues.apache.org/jira/browse/HIVE-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027219#comment-13027219
]
Ashutosh Chauhan commented on HIVE-2029:
----------------------------------------
+1 for removing 'hive.metastore.force.reload.conf'. Tests should not be written
in such a manner that they need to modify the code. This has opened up multiple
paths in Metastore code which needs to be reasoned about.
Is there an agreement on whether connectionURL hook should look for default DB
and create it in case it doesn't exist?
> 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
>
> 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
