Repository navigation
feat: add shared WAL record envelopes and payload validation - #381
Merged
Merged
Conversation
40 of 47 tasks
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
1 participant
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.
Summary
Replicas need to validate opaque ingestion payloads without decoding Arrow or copying the payload allocation. Add an independent
recordfeature with sharedBatchownership, a separately serializableBatchMeta, caller-bounded length checks and SHA-256 validation. Callers retain responsibility for routing, producer sequencing, control commands and durable commit.Fixed binary fixtures cover the record domain tags and metadata layout. CI enables the new feature; production ingestion is unchanged.
Refs #378.
Testing