Expose successful CSV source records to recovery handlers - #5
Merged
osipovartem merged 1 commit intoSep 17, 2026
Merged
osipovartem merged 1 commit into
osipovartem merged 1 commit into
Conversation
osipovartem
merged commit Sep 17, 2026
768a4e9
into
embucket-parquet-59.2.0-bounded-skip
22 of 26 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
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
Performance
The strict/default CSV decoder path is unchanged. Successful-record callbacks run only when a recovery handler is explicitly configured, where raw record bytes are already retained.
Validation
cargo +1.95.0 test -p arrow-csv --lib --offline(74 passed)cargo +1.95.0 clippy -p arrow-csv --lib --offline --no-deps -- -D warningscargo +1.95.0 fmt --all -- --check