HADOOP-18544: S3A: add option to disable probe for dir marker recreation on delete/rename. #5354
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.
Description of PR
In applications which do many single-file deletions on the same dir, a lot of time is wasted in maybeCreateFakeParentDirectory().
Proposed: add an option to disable the probe, for use by applications which are happy for parent dirs to sometimes disappear after a cleanup.
file by file delete is still woefully inefficient because of the HEAD request on every file, but there's no need to amplify the damage.
How was this patch tested?
The patch was tested against s3 bucket in US-West 2
For code changes:
Caveats:
Parent directories might disappear on delete or on renames.
What breaks:
The rename tests are failing for the FileContext renames as both S3AFileSystem and the FileContext have different probes and different rules.
LICENSE
,LICENSE-binary
,NOTICE-binary
files?