hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noritaka Sekiyama (Jira)" <>
Subject [jira] [Commented] (HIVE-12679) Allow users to be able to specify an implementation of IMetaStoreClient via HiveConf
Date Thu, 13 Aug 2020 13:15:00 GMT


Noritaka Sekiyama commented on HIVE-12679:

I talked with Austin, and I submitted a new pull-request based on the patch which has been
already uploaded to this issue.

Hive committers - can you review the patch again?

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