Repository navigation
feat: share validated Arrow IPC decoding for WAL materialization - #380
Merged
Merged
Conversation
42 of 49 tasks
beinan
marked this pull request as ready for review
October 19, 2026 05:13
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
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
Materializers need to decode replicated Arrow IPC without copying large binary payloads or bypassing format validation. Add an optional
ipc::decode(Bytes, expected_schema)module with shared input ownership, dictionary and multi-batch support, schema/block/array-buffer checks and row/count limits. Compressed IPC and dictionary deltas remain rejected until their expansion is budgeted. Reject foreign endianness and contain Arrow metadata panics in panic-unwind builds; panic-abort builds cannot recover from dependency panics.The component benchmark now calls this same decoder, including validation costs. Replication does not require the feature; production ingestion is not connected by this PR. Callers still reserve decoding workspace, and numeric alignment repair can allocate.
Refs #378.
Testing