HADOOP-13600 #167
Closed
HADOOP-13600 #167
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…x parallelism. Even listing and delete calls should be in parallel threads. Indeed: listing could consider doing a pre-emptive call to grab all of the list, though for a bucket with a few million files this would be too expensive. Really only need to be collecting at the same rate as copies, which is implicitly defined by the rate of keys added to a delete queue Change-Id: I906a1a15f3a7567cbff1999236549627859319a5
Change-Id: Ibfe08fb289deaa3b2fa21a8281f58651edb6d2ab
steveloughran
force-pushed
the
s3/HADOOOP-13600-rename
branch
from
00a0b79
to
b33b28c
Compare
This was referenced Apr 9, 2019
This was referenced Apr 25, 2019
This was referenced May 2, 2019
This was referenced May 9, 2019
This was referenced Jun 1, 2019
This was referenced Jun 8, 2019
This was referenced Jun 13, 2019
Merged
Closed
This was referenced Jun 21, 2019
shanthoosh
pushed a commit
to shanthoosh/hadoop
that referenced
this pull request
Oct 15, 2019
Author: Jacob Maes <jmaes@linkedin.com> Reviewers: Prateek Maheshwari <pmaheshw@linkedin.com>, Navina Ramesh <navina@apache.org> Closes apache#167 from jmakes/samza-1266
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
starting on parallel rename, still designing code for max parallelism. Even listing and delete calls should be in parallel threads. Really only need to be collecting at the same rate as copies, which is implicitly defined by the rate of keys added to a delete queue