planner: enhance rule partition pruning (#14544) #14546
Merged
Conversation
This file contains 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
XuHuaiyu
added
type/enhancement
imtbkcat
added
the
status/can-merge
|
Sorry @imtbkcat, you don't have permission to trigger auto merge event on this branch. |
|
/run-all-tests |
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.
cherry-pick #14544
What problem does this PR solve?
fix #14539
What is changed and how it works?
Use
ranger.DetachCondAndBuildRangeForIndexinstead ofranger.ExtractAccessConditionsForColumninpartitionProcessor.canBePruned.Because of that
ExtractAccessConditionsForColumnonly handles the scenario that the CNF/DNF only covers one column.Check List
Tests
Code changes
Side effects
N/A
Related changes
release-3.0
Release note
Enhance the logical rule partition pruning to cover more scenarios.