-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
tools: update the usage of region startkey to region keys #7637
Conversation
Signed-off-by: IcePigZDB <icepigzdb@gmail.com>
[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. |
Signed-off-by: IcePigZDB <icepigzdb@gmail.com>
Signed-off-by: IcePigZDB <icepigzdb@gmail.com>
/cc @TomShawn |
@IcePigZDB Since you have added a tickbox v5.4, is this a v5.4 feature? |
yes, if anything change, I will keep you informed. |
PTAL @TomShawn |
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 |
@TomShawn: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
/remove-status LGT1 |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 2476382
|
Signed-off-by: IcePigZDB icepigzdb@gmail.com
First-time contributors' checklist
What is changed, added or deleted? (Required)
Support endKey in http interface
regions/key
and adjust the pdctl region commandregion startKey
toregion keys
accordingly. This is originally proposed as a precondition of the push down optimisation ofinfomation_schema.tikv_region_status
.Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?