-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
planner: fix incorrect results when using a prefix index with OR condition (#21251) #21287
planner: fix incorrect results when using a prefix index with OR condition (#21251) #21287
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
/run-all-tests |
@Reminiscent please accept the invitation then you can push to the cherry-pick pull requests. |
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.
lgtm
@SunRunAway @lzmhhh123 PTAL |
/run-all-tests |
1 similar comment
/run-all-tests |
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.
LGTM
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
@ti-srebot merge failed. |
|
…ot/tidb into ti-srebot/release-4.0-06e99582d89b
/run-all-tests |
@SunRunAway @lzmhhh123 PTAL. Please help merge. Thanks! |
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
cherry-pick #21251 to release-4.0
What problem does this PR solve?
Issue Number: close #21234
Problem Summary:
In the previous implementation, when we use a prefix index with OR condition, it will fail to Cut Datum By PrefixLen.
What is changed and how it works?
When we use
detachDNFCondAndBuildRangeForIndex
function, we take prefix index into consideration.Check List
Tests
Release note