[
https://issues.apache.org/jira/browse/HADOOP-8649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433220#comment-13433220
]
Daryn Sharp commented on HADOOP-8649:
-------------------------------------
You may want to test if there's any incompatibilities with the chrooted
filesystem. If so, I wonder if it would be better as in more generalized, to
push the change down into {{FilterFileSystem}} or {{FileSystem}} itself.
Haven't thought it all the way through, but a compound filter may use an array
and each filesystem is given the opportunity to add additional filters.
If there's no problem with chroot, and you feel that's too much work, perhaps
it could be something for another jira.
> ChecksumFileSystem should have an overriding implementation of
> listStatus(Path, PathFilter) for improved performance
> --------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8649
> URL: https://issues.apache.org/jira/browse/HADOOP-8649
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 1.0.3, 2.0.0-alpha
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Attachments: branch1-HADOOP-8649.patch, branch1-HADOOP-8649.patch,
> HADOOP-8649_branch1.patch, HADOOP-8649_branch1.patch,
> HADOOP-8649_branch1.patch_v2, HADOOP-8649_branch1.patch_v3,
> TestChecksumFileSystemOnDFS.java, trunk-HADOOP-8649.patch,
> trunk-HADOOP-8649.patch
>
>
> Currently, ChecksumFileSystem implements only listStatus(Path).
> The other form of listStatus(Path, customFilter) results in parsing the list
> twice to apply each of the filters - custom and checksum filter.
> By using a composite filter instead, we limit the parsing to once.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
