[
https://issues.apache.org/jira/browse/HIVE-16172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904713#comment-15904713
]
Hive QA commented on HIVE-16172:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12857262/HIVE-16172.1.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 10336 tests passed
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/4062/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/4062/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-4062/
Messages:
{noformat}
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
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12857262 - PreCommit-HIVE-Build
> Switch to a fairness lock to synchronize HS2 thrift client
> ----------------------------------------------------------
>
> Key: HIVE-16172
> URL: https://issues.apache.org/jira/browse/HIVE-16172
> Project: Hive
> Issue Type: Bug
> Reporter: Tao Li
> Assignee: Tao Li
> Attachments: HIVE-16172.1.patch
>
>
> A synchronized block is used in
> "org.apache.hive.jdbc.HiveConnection.SynchronizedHandler.invoke(Object,
> Method, Object[])" to synchronize the client invocations. The problem is that
> it does not guarantee any fairness. One issue we were seeing is that a
> cancellation request was not able to be issued to HS2 until all the
> getOperationStatus() calls are finished from a while loop. Thus the
> cancellation cannot take effect.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
