Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 29 Aug 2013 21:33:51 +0000 (UTC)
From: "Sergey Shelukhin (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12666196.1377811773114.56519.1377812031677@arcas>
In-Reply-To: <JIRA.12666196.1377811773114@arcas>
References: <JIRA.12666196.1377811773114@arcas>
Subject: [jira] [Updated] (HIVE-5171) metastore server can cache pruning
 results across queries
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Shelukhin updated HIVE-5171:
-----------------------------------

    Assignee:     (was: Sergey Shelukhin)
    
> metastore server can cache pruning results across queries 
> ----------------------------------------------------------
>
>                 Key: HIVE-5171
>                 URL: https://issues.apache.org/jira/browse/HIVE-5171
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Sergey Shelukhin
>
> Partition pruning results are cached during a query (SemanticAnalyzer and ParseContext are the scope). 
> We could also cache them between queries in MetaStore, which would be especially useful if metastore server is remote and thus long-lived/shared between clients.
> It may be more complex than it seems due to OOM potential. Also the key would need to be changed since the same expression string that is currently used may mean different things for different queries.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira