PARQUET-990 More detailed error messages in footer parsing#408
Closed
ash211 wants to merge 1 commit into
Closed
Conversation
Include invalid values in exception messages when reading footer for two situations: - too-short files (include file length) - files with corrupted footer lengths (include calculated footer start index)
julienledem
approved these changes
May 12, 2017
julienledem
left a comment
julienledem
left a comment
Member
There was a problem hiding this comment.
This looks good to me.
can you create a corresponding PARQUET JIRA and prefix this PR with it's ID (PARQUET-XXX: More detailed error messages in footer parsing)
ash211
changed the title
Contributor
Author
|
Thanks @julienledem ! Filed as https://issues.apache.org/jira/browse/PARQUET-990 and updated this PR's title |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Include invalid values in exception messages when reading footer for two situations: