[
https://issues.apache.org/jira/browse/DRILL-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinfeng Ni resolved DRILL-4161.
-------------------------------
Resolution: Fixed
Fixed in commit:
https://git-wip-us.apache.org/repos/asf?p=drill.git;a=commit;h=bb3fc15216d9cab804fc9a6f0e5bd34597dd4394
> 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
>
> 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)
