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

["Thejas M Nair (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096992#comment-15096992 ] 

Thejas M Nair commented on HIVE-12679:
--------------------------------------

Note that SessionHiveMetaStoreClient implements logic for temp tables, as they have a lifetime of a session. I am wondering if this config should determine which IMetaStoreClient impl is used by SessionHiveMetaStoreClient, instead of replacing SessionHiveMetaStoreClient itself.
Some changes to SessionHiveMetaStoreClient would be needed as well for that approach, for it to accept configured IMetaStoreClient.

I am curious about the use case here. Are you interested in replacing the use of thrift server because of any particular issues you see with it ?
Note that you can use metastore server can be used in embedded mode, which means that the metastore client will effectively talk directly to the persistent store (RDBMS or HBase in case of hbase metastore). 

The hbase metastore work might possibly interest you - https://issues.apache.org/jira/browse/HIVE-9452, https://cwiki.apache.org/confluence/display/Hive/HBaseMetastoreDevelopmentGuide


> 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
>
> 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)