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 if an error occurs while parsing a CSV file the absolute line/row number is not part of the error message. Without the line number it can be very hard to determine where the incorrect value is especially in vary large files.
It would be good if the reader and parser could keep track of the row number and maybe line number when new lines are allowed in values so that they can be included in error message.
Currently if an error occurs while parsing a CSV file the absolute line/row number is not part of the error message. Without the line number it can be very hard to determine where the incorrect value is especially in vary large files.
It would be good if the reader and parser could keep track of the row number and maybe line number when new lines are allowed in values so that they can be included in error message.
Reporter: Nate Clark / @n3world
Assignee: Nate Clark / @n3world
PRs and other links:
Note: This issue was originally created as ARROW-12675. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: