hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-19873) Cleanup operation log on query cancellation after some delay
Date Tue, 12 Jun 2018 19:20:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-19873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510066#comment-16510066
] 

Sergey Shelukhin commented on HIVE-19873:
-----------------------------------------

Why does cancel use timeout of 0 on SQLOperation? 
Other than that looks ok pending tests.

> 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
>         Attachments: HIVE-19873.1.patch
>
>
> 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)

Mime
View raw message