hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-21484) Metastore API getVersion() should return real version
Date Thu, 21 Mar 2019 11:57:00 GMT


Hive QA commented on HIVE-21484:

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 7 failed/errored test(s), 15840 tests executed
*Failed tests:*
org.apache.hive.jdbc.TestActivePassiveHA.testActivePassiveHA (batchId=261)
org.apache.hive.jdbc.TestActivePassiveHA.testClientConnectionsOnFailover (batchId=261)
org.apache.hive.jdbc.TestActivePassiveHA.testConnectionActivePassiveHAServiceDiscovery (batchId=261)
org.apache.hive.jdbc.TestActivePassiveHA.testManualFailover (batchId=261)
org.apache.hive.jdbc.TestActivePassiveHA.testManualFailoverUnauthorized (batchId=261)
org.apache.hive.jdbc.TestActivePassiveHA.testNoConnectionOnPassive (batchId=261)
org.apache.hive.spark.client.TestSparkClient.testSyncRpc (batchId=331)

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.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 7 tests failed

This message is automatically generated.

ATTACHMENT ID: 12963198 - PreCommit-HIVE-Build

> Metastore API getVersion() should return real version
> -----------------------------------------------------
>                 Key: HIVE-21484
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>            Priority: Minor
>         Attachments: HIVE-21484.01.patch
> Currently I see the {{getVersion}} implementation in the metastore is returning a hard-coded
"3.0". It would be good to return the real version of the metastore server using {{HiveversionInfo}}
so that clients can take certain actions based on metastore server versions.
> Possible use-cases are:
> 1. Client A can make use of new features introduced in given Metastore version else stick
to the base functionality.
> 2. This version number  can be used to do a version handshake between client and server
in the future to improve our cross-version compatibity story.

This message was sent by Atlassian JIRA

View raw message