Fix ListObjectsV2 pagination to support listing more than 1000 objects #2652
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.
Problem
The
AwsObjectStorage.doList()
method only returned the first 1000 objects from S3's ListObjectsV2 API, which has a maximum response limit of 1000 objects per request. This caused issues when trying to list buckets with more than 1000 objects, as subsequent objects were silently ignored.According to the AWS ListObjectsV2 documentation:
The implementation should support listing all objects with a given prefix, regardless of the total count.
Solution
Implemented proper pagination support by:
listObjectsWithPagination()
helper methodresp.isTruncated()
to determine if more pages existresp.nextContinuationToken()
) to fetch subsequent pagesBefore:
After:
Testing
Added comprehensive test coverage:
Impact
This fix ensures that operations like log cleanup in
LogUploader
and other components that rely on listing objects will now work correctly with buckets containing more than 1000 objects.Closes #2650
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.