[
https://issues.apache.org/jira/browse/HIVE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346230#comment-14346230
]
Nemon Lou commented on HIVE-9839:
---------------------------------
Thanks [~vgumashta] for your comments.
Correct me if i am wrong:
For failed async queries,opHandle never pass back to client side for now.Only
HiveSQLException's message is passed back.So client side can not use opHandle
for later error reporting/operation status check.
HIVE-5799 is a possible solution,when opHandle expired/timed-out internal is
carefully configured .If the creation of orphan opHandles is much faster than
opHandle expired internal,we still need a complete fix (or fix the failed
queries in time).
Anyway,it's will be good to fix this issue directly.Though the way to fix it is
not clear for me now.
> 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)
