hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-14799) Query operation are not thread safe during its cancellation
Date Thu, 06 Oct 2016 10:09:20 GMT


Hive QA commented on HIVE-14799:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 10656 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: 1 tests failed

This message is automatically generated.

ATTACHMENT ID: 12831889 - PreCommit-HIVE-Build

> Query operation are not thread safe during its cancellation
> -----------------------------------------------------------
>                 Key: HIVE-14799
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>            Reporter: Chaoyu Tang
>            Assignee: Chaoyu Tang
>         Attachments: HIVE-14799.1.patch, HIVE-14799.2.patch, HIVE-14799.patch
> When a query is cancelled either via Beeline (Ctrl-C) or API call TCLIService.Client.CancelOperation,
SQLOperation.cancel is invoked in a different thread from that running the query to close/destroy
its encapsulated Driver object. Both SQLOperation and Driver are not thread-safe which could
sometimes result in Runtime exceptions like NPE. The errors from the running query are not
handled properly therefore probably causing some stuffs (files, locks etc) not being cleaned
after the query termination.

This message was sent by Atlassian JIRA

View raw message