[Feature] Support dynamic partition pruning (backport #30319) #49448
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.
Open-sourced table formats (e.g. hive) support data partitioning. That is to say, any record in a given data file has the same set of partition values.
This is a common practice for large fact tables (e.g.
lineorder
can be partitioned bylo_orderdate
in the SSB dataset ).If the predicates generated by the runtime filter (
lo_orderdate IN SET(...)
) can be applied to the partition columns, we could use this to test if a data file (i.e. scan range) can be skipped or not.SSB Q1
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check:
This is an automatic backport of pull request #30319 done by [Mergify](https://mergify.com). Open-sourced table formats (e.g. hive) support data partitioning. That is to say, any record in a given data file has the same set of partition values.
This is a common practice for large fact tables (e.g.
lineorder
can be partitioned bylo_orderdate
in the SSB dataset ).If the predicates generated by the runtime filter (
lo_orderdate IN SET(...)
) can be applied to the partition columns, we could use this to test if a data file (i.e. scan range) can be skipped or not.SSB Q1
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist: