hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-12679) Allow users to be able to specify an implementation of IMetaStoreClient via HiveConf
Date Wed, 24 Feb 2016 05:18:18 GMT


Hive QA commented on HIVE-12679:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 9822 tests executed
*Failed tests:*

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 4 tests failed

This message is automatically generated.

ATTACHMENT ID: 12789271 - PreCommit-HIVE-TRUNK-Build

> 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
>    Affects Versions: 2.1.0
>            Reporter: Austin Lee
>            Assignee: Austin Lee
>            Priority: Minor
>              Labels: metastore
>         Attachments: 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