Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Fri, 11 Dec 2015 19:36:47 +0000 (UTC)
From: "Jinfeng Ni (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12919046.1449254562000.241.1449862607078@Atlassian.JIRA>
In-Reply-To: <JIRA.12919046.1449254562000@Atlassian.JIRA>
References: <JIRA.12919046.1449254562000@Atlassian.JIRA>
 <JIRA.12919046.1449254562831@arcas>
Subject: [jira] [Updated] (DRILL-4161) Make Hive Metastore client caching
 user configurable.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jinfeng Ni updated DRILL-4161:
------------------------------
    Fix Version/s: 1.5.0

> Make Hive Metastore client caching user configurable.
> -----------------------------------------------------
>
>                 Key: DRILL-4161
>                 URL: https://issues.apache.org/jira/browse/DRILL-4161
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Jinfeng Ni
>             Fix For: 1.5.0
>
>
> Drill leverages LoadingCache in hive metastore client, in order to avoid the long access time to hive metastore server. However, there is a tradeoff between caching stale data and the possibility of cache hit. 
> For instance, DRILL-3893 changes cache invalidation policy to "1 minute after last write", to avoid the chances of hitting stale data. However, it also implies that the cached data would be only valid for 1 minute after loading/write.
> It's desirable to allow user to configure the caching policy, per their individual use case requirement. In particular, we probably should allow user to specify:
> 1) caching invalidation policy : expire after last access, or expire after last write.
> 2) cache TTL.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)