-
Notifications
You must be signed in to change notification settings - Fork 2.4k
fix: decide hash join dynamic filter production at planning time #24601
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
adriangb
merged 6 commits into
apache:main
from
pydantic:hashjoin-dynamic-filter-decide-at-planning-time
Aug 24, 2026
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
0cd4bd1
fix: decide hash join dynamic filter production at planning time
adriangb 2f5bede
test: cover re-running filter pushdown after a custom optimizer rule
adriangb 7e8184e
Update datafusion/physical-plan/src/joins/hash_join/exec.rs
adriangb c1301f2
refactor: make plan_contains_expression_id public
adriangb 3ea2b2a
docs: restore paragraph break and drop redundant execute() comment
adriangb 891f961
docs: note the Post phase re-run is an existing guarantee
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1122,7 +1122,12 @@ where | |
| /// | ||
| /// This traverses both the execution plan and the children of each expression root | ||
| /// reported by [`ExecutionPlan::apply_expressions`]. | ||
| pub(crate) fn plan_contains_expression_id( | ||
| /// | ||
| /// Producers of dynamic filters use this to find out whether anything downstream | ||
| /// holds the filter they pushed, since a node that replies | ||
| /// [`PushedDown::No`](crate::filter_pushdown::PushedDown::No) may still retain it | ||
| /// for statistics pruning. | ||
| pub fn plan_contains_expression_id( | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't love making this public just for another workspace member. Unfortunately no way around it (other than adding a |
||
| plan: &Arc<dyn ExecutionPlan>, | ||
| expression_id: u64, | ||
| ) -> Result<bool> { | ||
|
|
||
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
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.
Is it generally acceptable to re-run optimizer rules like this? Are they supposed to be idempotent?
Maybe this isn't something we should advertise if idempotency isn't guranteed generally for all optimizer rules.
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.
For this specific case we already assert it's idempotent:
post_phase_is_idempotent_on_hash_join.But in general no, I don't think it's safe to re-run optimizer rules. The
Prephase of filter pushdown for example is not idempotent w/pushdown_filters=false. In general I don't think we've defined the idempotency contract well enough across rules. And for filter pushdown in particular this is another example of why the current implementation ofpushdown_filters=falseis problematic.