-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Parquet: Use native getRowIndexOffset support instead of calculating it #11520
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
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
f435ca1
Parquet: Remove the row position since parquet row group has it natively
flyrain ffa7e61
Change ColumnarBatchReader for Spark 3.4 and 3.5
wypoon 832ee7a
Retain old methods but deprecate them, to avoid breaking the API.
wypoon 73d1380
Fix inadvertent renaming of a parameter.
wypoon 00a4b3c
Fix inadvertent dropping of a final method modifier.
wypoon ff29af6
Update deprecation comments.
wypoon d189412
Throw an exception if PageReadStore does not have the row index offset.
wypoon 661b264
Address nit.
wypoon File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Is there a better Exception than
IllegalArgumentException? IsIllegalStateExceptiona bit better?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can see why you might consider
IllegalStateException. I do thinkIllegalArgumentExceptionis appropriate, because thePageReadStoreis an argument to the method being called, and the problem is with thePageReadStore. I thinkIllegalStateExceptionis typically used to indicate an internal inconsistency in the module.Consider if we use Guava's
Preconditionsto check a condition here. The condition would be thatsource.getRowIndexOffset().isPresent(). ThecheckArgumentmethods throwIllegalArgumentExceptionand "Ensures the truth of an expression involving one or more parameters to the calling method." ThecheckStatemethods throwIllegalStateExceptionand "Ensures the truth of an expression involving the state of the calling instance, but not involving any parameters to the calling method." (my emphasis)Of course, that just expresses the opinions of the authors of Guava. There are others who might argue that
IllegalStateExceptionis appropriate here, or neitherIllegalStateExceptionnorIllegalArgumentException. It really doesn't matter too much. I can just throwRuntimeExceptionif you do not agree withIllegalArgumentException.