[
https://issues.apache.org/jira/browse/HIVE-19873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasanth Jayachandran updated HIVE-19873:
-----------------------------------------
Description:
When a query is executed using beeline and the query is cancelled due to query
timeout or kill query or triggers and when there is cursor on operation log row
set, the cursor can thrown an exception as cancel will cleanup the operation
log in the background. This can return a non-zero exit code in beeline. Query
cancellation on success should return exit code 0.
Adding a delay to the cleanup of operation logging in operation cancel can
avoid the close during read.
was:When a query is executed using beeline and the query is cancelled due to
query timeout or kill query or triggers and when there is cursor on operation
log row set, the cursor can thrown an exception as cancel will cleanup the
operation log in the background. This can return a non-zero exit code in
beeline. So add a delay to the cleanup of operation logging in operation
cancel.
> Cleanup operation log on query cancellation after some delay
> ------------------------------------------------------------
>
> Key: HIVE-19873
> URL: https://issues.apache.org/jira/browse/HIVE-19873
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Affects Versions: 3.1.0, 4.0.0
> Reporter: Prasanth Jayachandran
> Assignee: Prasanth Jayachandran
> Priority: Major
>
> When a query is executed using beeline and the query is cancelled due to
> query timeout or kill query or triggers and when there is cursor on operation
> log row set, the cursor can thrown an exception as cancel will cleanup the
> operation log in the background. This can return a non-zero exit code in
> beeline. Query cancellation on success should return exit code 0.
> Adding a delay to the cleanup of operation logging in operation cancel can
> avoid the close during read.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
