Get object sizes based on S3's ListObjects output (just with scan_object_sizes() to start with) #2248
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.
Monday: 8560764974
Limited to just
scan_object_sizes
to start with, to show the idea.Calculate object sizes using functionality in the storage backend itself when possible. This PR calculates compressed sizes on S3 based on the
ListObjectsV2
output, so we don't need to read all the keys.For storages where we haven't implemented anything fancy, just read all the (compressed) keys and check the compressed size on their header.
Remaining work:
scan_object_sizes_by_stream
scan_object_sizes_for_stream
AdminTools
Python API on the v2 API, including search by regex. Docs page to explain the output.