hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-10835) Concurrency issues in JDBC driver
Date Thu, 28 May 2015 06:10:17 GMT


Hive QA commented on HIVE-10835:

{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:

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

Test results:
Console output:
Test logs:

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: 2 tests failed

This message is automatically generated.

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

> Concurrency issues in JDBC driver
> ---------------------------------
>                 Key: HIVE-10835
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 1.2.0
>            Reporter: Chaoyu Tang
>            Assignee: Chaoyu Tang
>         Attachments: HIVE-10835.patch
> Though JDBC specification specifies that "Each Connection object can create multiple
Statement objects that may be used concurrently by the program", but that does not work in
current Hive JDBC driver. In addition, there also exist  race conditions between DatabaseMetaData,
Statement and ResultSet as long as they make RPC calls to HS2 using same Thrift transport,
which happens within a connection.
> So we need a connection level lock to serialize all these RPC calls in a connection.

This message was sent by Atlassian JIRA

View raw message