Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 22 Oct 2015 20:13:27 +0000 (UTC)
From: "Chaoyu Tang (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.12905255.1444928561000.32783.1445544807696@Atlassian.JIRA>
In-Reply-To: <JIRA.12905255.1444928561000@Atlassian.JIRA>
References: <JIRA.12905255.1444928561000@Atlassian.JIRA>
 <JIRA.12905255.1444928561582@arcas>
Subject: [jira] [Commented] (HIVE-12187) Release plan once a query is
 executed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chaoyu Tang commented on HIVE-12187:
------------------------------------

[~jxiang] The patch looks good to me, except I am not quite sure about saving the locks in close() method. Do you know under what circumstance that there are some locks left from last query and should be preserved? Thanks

> 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)