-
Notifications
You must be signed in to change notification settings - Fork 1.9k
use ProjectionExprs:project_statistics in FileScanConfig #19094
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
11 commits
Select commit
Hold shift + click to select a range
2ec02bb
use ProjectionExprs:project_statistics in FileScanConfig
adriangb 0749b04
simplify
adriangb 671b4d1
fix tests
adriangb 8ea4096
fix tests
adriangb 6e1de65
fmt
adriangb 08533b5
fix tests, deprecate unused methods
adriangb 396a47d
add note
adriangb 1bd7e19
fmt
adriangb 9bf832b
fix tests
adriangb 260655c
remove tests that were only testing a test-only function
adriangb d13a88c
Update file_scan_config.rs
adriangb 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
Oops, something went wrong.
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.
I'm trying to understand why these numbers changed. I think the issue is that the way the row sizes are calculated when the statistics are initially computed doesn't match how the row sizes are calculated by
ProjectionExprs. I'm guessing they're measuring different things (parquet row size vs arrow row size??). Unfortunately theStatisticsstruct doesn't have much in terms of documentation.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.
Indeed this is the case:
datafusion/datafusion/datasource-parquet/src/metadata.rs
Line 253 in 388db0e
So the initial collection just adds up the size of the row groups (in Parquet). But presumably we want the size to be the size returned by the scan, not the size of the scan itself. So this is wrong, it should be doing the same calculation as
ProjectionExprs.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'm going to include a fix in this PR so that the original collection matches 😄
Uh oh!
There was an error while loading. Please reload this page.
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 agree using "bytes of arrow data" sounds better compared to "bytes of parquet encoded data"
i would have thought the difference is due to your fixing this:
(BTW I think you could mark this PR as fixing that issue as well)Edit: I see you did!