hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rentao Wu (JIRA)" <>
Subject [jira] [Commented] (HIVE-12679) Allow users to be able to specify an implementation of IMetaStoreClient via HiveConf
Date Fri, 01 Dec 2017 19:57:00 GMT


Rentao Wu commented on HIVE-12679:

I would like to bring up this JIRA again for consideration as it allows for alternative metastore
clients such to AWS Glue DataCatalog. Would the approach of changing SessionHiveMetastoreClient
to have a delegate implementation of IMetastoreClient work? (Removing inheritance of extending
HiveMetastoreClient impl) If that is fine approach I'll work on a new patch for this.

> Allow users to be able to specify an implementation of IMetaStoreClient via HiveConf
> ------------------------------------------------------------------------------------
>                 Key: HIVE-12679
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Configuration, Metastore, Query Planning
>            Reporter: Austin Lee
>            Assignee: Rentao Wu
>            Priority: Minor
>              Labels: metastore
>         Attachments: HIVE-12679.1.patch, HIVE-12679.2.patch, HIVE-12679.patch
> 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 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

View raw message