[
https://issues.apache.org/jira/browse/HIVE-14799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15553026#comment-15553026
]
Sergey Shelukhin commented on HIVE-14799:
-----------------------------------------
New patch mostly looks good. I was suggesting we move to the model where only
one thread from the driver manages all the resources except before it's
started, but I guess the current model also works.
There's a typo in description ("until")
+1
[~ashutoshc] do you also want to take a look?
> Query operation are not thread safe during its cancellation
> -----------------------------------------------------------
>
> Key: HIVE-14799
> URL: https://issues.apache.org/jira/browse/HIVE-14799
> 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
(v6.3.4#6332)