[
https://issues.apache.org/jira/browse/HADOOP-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931318#comment-15931318
]
ASF GitHub Bot commented on HADOOP-13371:
-----------------------------------------
GitHub user steveloughran opened a pull request:
https://github.com/apache/hadoop/pull/204
HADOOP-13371 S3a Globber, WiP
This is what I'd done up to the point I stopped looking at it; copies over
the FileSystem.globber and then adds an initial scale test.
1. I think we could do a great scale test against the landsat repo
1. I chose not to try and tweak the FileSystem.globber class for
subclassing, so we can do much more in here, and to set things up for having a
globStatus call which would return a remote iterator rather than an array
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/steveloughran/hadoop s3/HADOOP-13371-globber
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hadoop/pull/204.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #204
----
commit e4c7c50c67b17e68fe03f76ac88eba20946474a3
Author: Steve Loughran <[email protected]>
Date: 2016-08-19T20:53:36Z
HADOOP-13371 S3A globber
commit a99ffb8f5424499209cafc2a62579260e7a0796e
Author: Steve Loughran <[email protected]>
Date: 2017-03-18T18:32:23Z
HADOOP-13371 sync up with latest branch-2
----
> S3A globber to use bulk listObject call over recursive directory scan
> ---------------------------------------------------------------------
>
> Key: HADOOP-13371
> URL: https://issues.apache.org/jira/browse/HADOOP-13371
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs, fs/s3
> Affects Versions: 2.8.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
>
> HADOOP-13208 produces O(1) listing of directory trees in
> {{FileSystem.listStatus}} calls, but doesn't do anything for
> {{FileSystem.globStatus()}}, which uses a completely different codepath, one
> which does a selective recursive scan by pattern matching as it goes down,
> filtering out those patterns which don't match. Cost is
> O(matching-directories) + cost of examining the files.
> It should be possible to do the glob status listing in S3A not through the
> filtered treewalk, but through a list + filter operation. This would be an
> O(files) lookup *before any filtering took place*.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
