Gracefully handle malformed fields with trailing bytes in the data #413
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
One of my users recently shared a bug where they couldn't read INT64 columns exported from Oracle: mukunku/ParquetViewer#81
The error being:
At the time I investigated this issue and concluded that the file must be malformed. But I've been monitoring for this exception since then and I've noticed a few more users continuing to get the same error:
I also noticed other libraries don't seem to have issues opening this file. So even though the file is malformed in my opinion, would it still be worth gracefully processing such malformed fields so parquet-dotnet doesn't fall behind the competition? I mean, even if a file is malformed, if other libraries are supporting it but parquet-dotnet isn't that might cause people to prefer other libraries over this one.
However if this PR doesn't make sense I'm happy to close it out. Just wanted to get your opinion.