You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Austin Lee (JIRA)" <ji...@apache.org> on 2016/02/17 23:47:18 UTC

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

     [ https://issues.apache.org/jira/browse/HIVE-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Austin Lee updated HIVE-12679:
------------------------------
    Labels: metastore  (was: )

> 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
>            Assignee: Austin Lee
>            Priority: Minor
>              Labels: metastore
>             Fix For: 1.2.1
>
>
> 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
(v6.3.4#6332)