Enrich errors with table name for format or parsing errors
- Dominant language
- Rust
- Stars
- 9.3k
- Forks
- 2.4k
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 344
Description
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.**
It would be really nice to have ability to identify which table actually produced parsing or format (csv/json/etc) errors.
I mean errors like: `Error while parsing value X for column 1 at line 1` or `incorrect number of fields for line X, expected Y got Z` should point to table.
**Describe the solution you'd like**
Some kinds of errors should contain additional field, like `table_name`.
**Describe alternatives you've considered**
As an option, introduce or split current error type to something like: `input data error`. Not sure yet
**Additional context**
Looks like it requires a lot of efforts and will affect `arrow-rs`.
Contributor guide
Research direction
The issue names no files or tests; start by tracing the parsing and format-error paths in DataFusion and the affected arrow-rs paths. Determine which CSV/JSON parsing and field-count failures can carry a table name, then define the accepted error shape and verify that those failures identify their source table.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100