Add recoverable CSV record error handler - #3
Merged
osipovartem merged 1 commit intoSep 17, 2026
Merged
Conversation
Author
|
Performance evidence: Criterion on the existing 4-column, 4,096-row CSV reader benchmark measured 329.91 us before and 333.16 us after (+0.96%). Criterion classified the result as within the noise threshold. The no-handler path retains the original strict decoder loop; recovery allocations remain opt-in. |
osipovartem
merged commit Sep 17, 2026
4aee61a
into
embucket-parquet-59.2.0-bounded-skip
24 of 28 checks passed
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
CsvRecordErrorHandlerto the Arrow CSV readerWhy
DataFusion consumers implementing Snowflake-compatible
COPY ... VALIDATION_MODEneed to report malformed CSV rows and continue scanning later valid rows. Arrow currently aborts on the first field-count mismatch and discards the source record metadata.Performance
The default path dispatches once per input chunk and then executes the existing strict decoder loop unchanged. Raw record retention and recovery allocations are enabled only when a handler is explicitly configured.
Tests
73 tests passed, including chunk-boundary recovery for both extra and missing fields.