[HIVE-12679] Allow users to be able to specify an implementation of IMetaStoreClient via HiveConf

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: Configuration, Metastore, Query Planning
• Labels: metastore pull-request-available
• Assignee: Shohei Okumiya
• Reporter: Austin Lee
• Created: 15/Dec/15 21:25
• Updated: 22/Jan/24 02:18

Description

Hi,

I would like to propose a change that would make it possible for users to choose an implementation of IMetaStoreClient via HiveConf, i.e. hive-site.xml. Currently, in Hive the choice is hard coded to be SessionHiveMetaStoreClient in org.apache.hadoop.hive.ql.metadata.Hive. There is no other direct reference to SessionHiveMetaStoreClient other than the hard coded class name in Hive.java and the QL component operates only on the IMetaStoreClient interface so the change would be minimal and it would be quite similar to how an implementation of RawStore is specified and loaded in hive-metastore. One use case this change would serve would be one where a user wishes to use an implementation of this interface without the dependency on the Thrift server.

Thank you,
Austin

Issue Links

• is related to: HIVE-27473 Make SessionHiveMetaStoreClient and HiveMetaStoreClientWithLocalCache composable
• links to: GitHub Pull Request #1402
• links to: GitHub Pull Request #4444