Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RecordProcessingException: access to column position in chars #78

Open
jods4 opened this issue Nov 16, 2021 · 0 comments
Open

RecordProcessingException: access to column position in chars #78

jods4 opened this issue Nov 16, 2021 · 0 comments

Comments

@jods4
Copy link

jods4 commented Nov 16, 2021

Is your feature request related to a problem? Please describe.
When a large file fails to parse, it would greatly help to be able to precisely locate where the error is in the file.
Row-wise this is covered by RecordContext.PhysicalRecordNumber.
Column-wise I thought it would be covered by ColumnContext.PhysicalIndex but it's an index, not a column number.

Describe the solution you'd like
Add ColumnContext.PhysicalPosition or similar.

Describe alternatives you've considered
As mentionned above, we used ColumnContext.PhysicalIndex, but it's not enough to find the error position without referring to the specifications to determine the exact position of the faulty column.

Additional context
E.g. in a failing file, our message says the error is in Column 4 (which is correct, as in the "4th data column") but inside the file it was at position 19, which would have been helpful to have.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant