[COST-5216] Delete filtering optimization #5197
Merged
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.
Jira Ticket
COST-5216
Description
This change will switch us to using head_object to download only the metadata during the delete filtering instead of the s3 object. This will save us some time since we will no longer need to spend cycles retrieving the additional attributes available to the object from s3 such as the ACL, owner, storage type, etc.
Testing
I wrote a little test script we can use for this:
https://gist.github.com/myersCody/0c57dc2132a7a712c035ae1210c30d20
Output:
Release Notes