Expose recoverable CSV record diagnostics - #101
Merged
Merged
Conversation
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
CsvRecordErrorHandlerthroughCsvFormatandCsvSourceDepends on Embucket/arrow-rs#3.
Performance
The handler is optional and defaults to
None. Normal CSV scans retain existing repartitioning and Arrow's strict decoder fast path. Record retention and recovery work occur only for consumers that explicitly install a handler.Tests
The integration test covers valid rows before/after extra- and missing-field records, exact callback offsets, and diagnostic-mode repartitioning behavior.