-
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) #36704
executor,store/copr: fix index merge, distsql request's key ranges should be sorted (#36633) #36704
Conversation
Signed-off-by: ti-srebot <[email protected]>
[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. |
/run-all-tests |
@tiancaiamao you're already a collaborator in bot's repo. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 5d3f776
|
Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/5d3f776493efbb50dea2e5704f8f997e33c7accb |
cherry-pick #36633 to release-6.2
You can switch your code base to this Pull Request by using git-extras:
# In tidb repo: git pr https://github.com/pingcap/tidb/pull/36704
After apply modifications, you can push your change to this PR via:
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.