hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Work logged] (HIVE-12679) Allow users to be able to specify an implementation of IMetaStoreClient via HiveConf
Date Fri, 28 Aug 2020 10:20:00 GMT


ASF GitHub Bot logged work on HIVE-12679:

                Author: ASF GitHub Bot
            Created on: 28/Aug/20 10:19
            Start Date: 28/Aug/20 10:19
    Worklog Time Spent: 10m 
      Work Description: moomindani edited a comment on pull request #1402:

   @sankarh Thank you for the comment, I will try to address it.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 475789)
    Time Spent: 1h 10m  (was: 1h)

> 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: Noritaka Sekiyama
>            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: 1h 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