[HIVE-2029] MetaStore ConnectionURL updates need to trigger creation of Default DB if it doesn't exist

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.7.0
• Component/s: Metastore
• Assignee: Unassigned
• Reporter: Carl Steinbach
• Created: 07/Mar/11 10:36
• Updated: 23/Oct/11 20:20

Description

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.

Issue Links

• is blocked by: HIVE-2084 Upgrade datanucleus from 2.0.3 to a more recent version (3.?)
• is related to: HIVE-1939 Fix test failure in TestContribCliDriver/url_hook.q
• is related to: HIVE-1219 More robust handling of metastore connection failures