You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when a row does not have the correct number of columns an error is generated and parsing stops. It would be better if this behavior was customizable depending on the caller so that rows could either be ignored or altered to have the correct column count.
Ideally there would be some builtin handlers for this but it would be good for the caller to be able to implement their own handler if they wanted to collect the malformed rows and report them to a different component or maybe add fields based on the existing fields in the row.
Currently when a row does not have the correct number of columns an error is generated and parsing stops. It would be better if this behavior was customizable depending on the caller so that rows could either be ignored or altered to have the correct column count.
Ideally there would be some builtin handlers for this but it would be good for the caller to be able to implement their own handler if they wanted to collect the malformed rows and report them to a different component or maybe add fields based on the existing fields in the row.
Reporter: Nate Clark / @n3world
Assignee: Nate Clark / @n3world
Related issues:
PRs and other links:
Note: This issue was originally created as ARROW-12673. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: