Skip to content

Conversation

@steveloughran
Copy link
Contributor

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

…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 steveloughran force-pushed the s3/HADOOOP-13600-rename branch from 00a0b79 to b33b28c Compare November 28, 2016 14:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant