fix(s3): fix incorrect md5 for list operations#7298
Merged
Xuanwo merged 1 commit intoapache:mainfrom Mar 24, 2026
Merged
Conversation
dosubot
Bot
added
size:XS
Xuanwo
approved these changes
Mar 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Which issue does this PR close?
Closes #7297
Rationale for this change
As described in the issue, we're now referring MD5 from ETag and set it to returned object metadata.
But checking doc (link attached in the issue), all involved list operations don't return MD5, which means we're returning incorrect metadata.
What changes are included in this PR?
The MD5 field in the object metadata is optional, so in this PR I simply leave it empty.
Are there any user-facing changes?
No.
AI Usage Statement
No AI involvement.