[
https://issues.apache.org/jira/browse/HIVE-12187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968114#comment-14968114
]
Jimmy Xiang commented on HIVE-12187:
------------------------------------
The change to the locks is to avoid some lock leakage actually. So my question
is actually is to confirm that the leakage is not intentional.
The lock releasing behavior is not changed at all. When a new query is
executed, a new Context object is created. At this moment, without the patch,
if the locks in the old Context are not released, we can not access them any
more from the Context. With the patch, we save the locks, if any, in a new
list, so that we can release them later.
> Release plan once a query is executed
> --------------------------------------
>
> Key: HIVE-12187
> URL: https://issues.apache.org/jira/browse/HIVE-12187
> Project: Hive
> Issue Type: Improvement
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Fix For: 1.3.0, 2.0.0
>
> Attachments: HIVE-12187.1.patch, HIVE-12187.2.patch
>
>
> Some clients leave query operations open for a while so that they can
> retrieve the query results later. That means the allocated memory will be
> kept around too. We should release those resources not needed for query
> execution any more once it is executed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
