[
https://issues.apache.org/jira/browse/HIVE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345660#comment-14345660
]
Vaibhav Gumashta commented on HIVE-9839:
----------------------------------------
[~nemon] On a quick pass, this won't be an acceptable solution, as for async
queries, HiveSessionImpl#executeStatementInternal will return immediately but
the opHandle is required for later error reporting/operation status check. Let
me go over the code a bit more though to add more comments.
> HiveServer2 leaks OperationHandle on failed async queries
> ---------------------------------------------------------
>
> Key: HIVE-9839
> URL: https://issues.apache.org/jira/browse/HIVE-9839
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Affects Versions: 0.14.0, 0.13.1, 1.0.0
> Reporter: Nemon Lou
> Attachments: hive-9839.patch
>
>
> Using beeline to connect to HiveServer2.And type the following:
> drop table if exists table_not_exists;
> select * from table_not_exists;
> There will be an OperationHandle object staying in HiveServer2's memory for
> ever even after quit from beeline .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
