Repository navigation
fix: preserve TopK dynamic filters across recursive CTE iterations - #26670
Open
Kristofferjoha wants to merge 5 commits into
Open
Kristofferjoha wants to merge 5 commits into
Kristofferjoha wants to merge 5 commits into
Conversation
Kristofferjoha
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Which issue does this PR close?
Closes #26642.
Rationale for this change
TopK dynamic filters inside recursive CTEs stop updating the scan because
SortExec::reset_state()creates a new filter on each iteration, while the scan still references the original one. This prevents pruning during recursive queries.What changes are included in this PR?
DynamicFilterPhysicalExpr.cte.slt.Depends on #26056 for
DynamicFilterPhysicalExpr::reset(). It hasn't been merged yet, but it has been approved, so I based this change on its implementation.What is the testing strategy for this PR?
The new
cte.sltcase checks that the recursive query returns 1–4 and that the Parquet scan outputs 30 rows instead of 300, pruning 27 row groups across three iterations.Are there any user-facing changes?
No.