-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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: fix show table regions bug (#19562) #19895
executor: fix show table regions bug (#19562) #19895
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
/run-all-tests |
@3pointer 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
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
/run-all-tests |
/run-all-tests |
cherry-pick #19562 to release-4.0
What problem does this PR solve?
close: pingcap/br#477
Problem Summary:
when the last region has the endKey is as same as the range endKey. show table regions will return
ERROR 1105 (HY000): PD returned no region
errorWhat is changed and how it works?
What's Changed:
break when last scan region has same endkey with range endKey.
How it Works:
it won't scan next round, and return immediately
Related changes
Check List
Tests
before this commit:
MySQL [d]> show table t1 regions; ERROR 1105 (HY000): PD returned no region
with this commit:
works well
Release note