[v26.2.x] ct/l0: preserve the produce-time record crc on the read path - #31389
Merged
andrwng merged 1 commit intoJul 31, 2026
Merged
Conversation
Previously, when L0 materialized record batches from the payloads in object storage, we were resetting the record-batch crc and rederiving it from the materialized payload data, rather than using the crc in object storage that were written at produce time. This meant that we wouldn't have detected a corrupted bit at rest when served from object storage. Updates the record-batch materialization code to use the record-batch crc and only recompute the header_crc (needed since neither the placeholder nor the object storage batch have the full materialized-batch header_crc with correct offset and size). (cherry picked from commit 4be7193)
Collaborator
Author
CI test resultstest results on build#88044
|
andrwng
approved these changes
Jul 31, 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
3 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.
Backport of PR #31375