[
https://issues.apache.org/jira/browse/HIVE-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HIVE-12679:
----------------------------------
Labels: metastore pull-request-available (was: metastore)
> Allow users to be able to specify an implementation of IMetaStoreClient via
> HiveConf
> ------------------------------------------------------------------------------------
>
> Key: HIVE-12679
> URL: https://issues.apache.org/jira/browse/HIVE-12679
> Project: Hive
> Issue Type: Improvement
> Components: Configuration, Metastore, Query Planning
> Reporter: Austin Lee
> Priority: Minor
> Labels: metastore, pull-request-available
> Attachments: HIVE-12679.1.patch, HIVE-12679.2.patch,
> HIVE-12679.branch-1.2.patch, HIVE-12679.branch-2.3.patch, HIVE-12679.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
