-
Notifications
You must be signed in to change notification settings - Fork 253
CLDSRV-872: store checksum in object metadata #6113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
leif-scality
wants to merge
8
commits into
development/9.4
from
development/CLDSRV-872-store-checksum-in-object-metadata
+2,418
−101
Closed
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
4838bb0
CLDSRV-863: bump arsenal to 8.3.6
leif-scality 464f12d
CLDSRV-863: handle NoSuchKey error in isCompleteMPUInProgress
leif-scality 09435e2
CLDSRV-863: emit trailer in TrailingChecksumTransform
leif-scality 7c7367d
CLDSRV-863: handle trailer headers and add new trailer errors
leif-scality 588f37e
CLDSRV-863: add ChecksumTransform to calculate and verify stream chec…
leif-scality 176ee41
CLDSRV-863: pipe requests to ChecksumTransform and validate checksum …
leif-scality 888ea43
CLDSRV-863: PutObject/UploadPart checksum service tests
leif-scality 85e28c8
CLDSRV-872: store checksum in metadata for objects uploaded with PutO…
leif-scality File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In
getChecksumDataFromHeaders, when no checksum headers and no trailer are present, this defaults tocrc64nvme. This means every PutObject request (even those not requesting checksum validation) will now compute a CRC64NVME hash of the entire body. This is an intentional design choice (always store a checksum in metadata), but it is a performance change — every put now pays the cost of CRC64NVME computation. Worth documenting this behavioral change.— Claude Code