[BugFix] Cached fragment misuses exogenous runtime filter (backport #51150) #51202
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.
Why I'm doing:
Cached fragment(Fragment 0) should not use exogenous runtime filters produced by remote fragment(Fragment 2's HashJoin(2) ), since the HashJoin(2)'s runtime filter changes as its the right side changes. so we should disable query cache in this situation.
When we take this into conderation , we use PlanFragment.get{Build,Probe}RuntimeFilters methods to obtain fragment-specific runtime filter informations that are not be collected before using.
What I'm doing:
Collection runtime filter build/probe information in PlanFragmentBuilder
Fixes #issue
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 #51150 done by [Mergify](https://mergify.com). ## Why I'm doing: ![image](https://github.com/user-attachments/assets/49eb87f9-97b5-40ca-9804-7f6519c4e19b) Cached fragment(Fragment 0) should not use exogenous runtime filters produced by remote fragment(Fragment 2's HashJoin(2) ), since the HashJoin(2)'s runtime filter changes as its the right side changes. so we should disable query cache in this situation.
When we take this into conderation , we use PlanFragment.get{Build,Probe}RuntimeFilters methods to obtain fragment-specific runtime filter informations that are not be collected before using.
What I'm doing:
Collection runtime filter build/probe information in PlanFragmentBuilder
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist: