-
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
executor,store/copr: fix index merge, distsql request's key ranges should be sorted #36633
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/d4c3a10ce74a3e8cf72e2ffa7ebf8a81aa400177 |
Verified in the integration test, now just keep the fixing part. |
7af7844
to
30dca2f
Compare
@@ -581,3 +582,49 @@ func TestAdaptiveClosestRead(t *testing.T) { | |||
// 2 IndexScan with cost 19/56, 2 TableReader with cost 32.5/65. | |||
checkMetrics("select/* +USE_INDEX_MERGE(t) */ id from t use index(`idx_v_s1`) use index(idx_s2) where (s1 < 3 and v > 0) or s2 = 3;", 3, 1) | |||
} | |||
|
|||
func TestCoprocessorPagingReqKeyRangeSorted(t *testing.T) { |
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.
The added test can only cover (literally) the added code.
It can't prevent regression in the future when code changes.
/merge |
This pull request has been accepted and is ready to merge. Commit hash: b220e23
|
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-6.2 in PR #36704 |
TiDB MergeCI notify
|
What problem does this PR solve?
Issue Number: close #36632
Problem Summary:
What is changed and how it works?
The key range for distsql request should be sorted!
Because locate region for the key ranges use a binary search pattern.
Check List
Tests
This bug is found by our integration test.
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.