You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Vishwajeet Dusane (JIRA)" <ji...@apache.org> on 2016/03/03 12:39:18 UTC
[jira] [Updated] (HADOOP-12876) [Azure Data Lake] Support for
process level FileStatus cache to optimize GetFileStatus frequent opeations
[ https://issues.apache.org/jira/browse/HADOOP-12876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vishwajeet Dusane updated HADOOP-12876:
---------------------------------------
Issue Type: Improvement (was: New Feature)
> [Azure Data Lake] Support for process level FileStatus cache to optimize GetFileStatus frequent opeations
> ---------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-12876
> URL: https://issues.apache.org/jira/browse/HADOOP-12876
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs, fs/azure, tools
> Reporter: Vishwajeet Dusane
> Assignee: Vishwajeet Dusane
>
> Add support to cache GetFileStatus and ListStatus response locally for limited period of time. Local cache for limited period of time would optimize number of calls for GetFileStatus operation.
> One of the example where local limited period cache would be useful - terasort ListStatus on input directory follows with GetFileStatus operation on each file within directory. For 2048 input files in a directory would save 2048 GetFileStatus calls during start up (Using the ListStatus response to cache FileStatus instances).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)