[
https://issues.apache.org/jira/browse/HIVE-22905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039977#comment-17039977
]
Hive QA commented on HIVE-22905:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12993793/HIVE-22905.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 18026 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/20728/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/20728/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-20728/
Messages:
{noformat}
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
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12993793 - PreCommit-HIVE-Build
> Transaction is not aborted when query cancelled, only when session is closed
> ----------------------------------------------------------------------------
>
> Key: HIVE-22905
> URL: https://issues.apache.org/jira/browse/HIVE-22905
> Project: Hive
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 3.1.2
> Reporter: Aron Hamvas
> Assignee: Aron Hamvas
> Priority: Major
> Attachments: HIVE-22905.patch
>
>
> Reproduction:
> # Start HMS
> # Start HS2
> # Start beeline
> # Execute a query and cancel query after transaction is started and before
> locks are acquired (yeah, that will take a debugger with breakpoints in
> DbLockManager)
> # Do not terminate Hive session
> DbLockManager will keep spinning in the checkLock loop as long as the Hive
> session is not closed since abortTxns is not invoked on HMS, and until the
> lock is acquired (even though the query could have been canceled long time
> ago).
> Driver only checks in close() method if there are locks acquired but it does
> not check if a txn is open.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)