-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Prune unread nested parquet leaves when a projected column is cast to a narrower type (nested schema pruning) #23398
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
Draft
adriangb
wants to merge
4
commits into
apache:main
Choose a base branch
from
pydantic:nested-schema-pruning
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
c153c6a
bench: parquet scan with a table schema narrower than a nested column
adriangb 5e737f2
refactor: extract parquet projection read plan into its own module
adriangb 71f5cd2
feat: prune unread nested parquet leaves when a projected column is c…
adriangb 5e55b4f
bench: add pruning-disabled variants to parquet_nested_schema_pruning
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
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.
This flag is responsible for a large share of the PR's surface: the six
proto-*files,parquet_writer.rs,file_formats.rs,information_schema.slt,configs.md, and the threading throughsource -> morselizer -> PreparedParquetOpen -> opener -> DecoderProjection. It's also what triggers thecargo-semver-checksmajor-version failure CI already reported (new pub field on the externally-constructibleParquetOptions).The PR description itself notes there's "no scenario where a correctly-working clip should be disabled" and that the flag could be deprecated after a release or two. For a change that's semantically invisible (IO reduction only, worst case = today's behavior), a permanent serialized knob seems disproportionate.
Options, roughly in order of preference:
Happy to be wrong if there's a concrete reason it must be plan-serialized, but as-is it roughly doubles the file count and forces a major-version bump for an optimization that's invisible to results.