Skip to content

tools: update the usage of region startkey to region keys (#6951)#8611

Merged
ti-chi-bot merged 17 commits intopingcap:release-6.0from
ti-chi-bot:cherry-pick-6951-to-release-6.0
May 13, 2022
Merged

tools: update the usage of region startkey to region keys (#6951)#8611
ti-chi-bot merged 17 commits intopingcap:release-6.0from
ti-chi-bot:cherry-pick-6951-to-release-6.0

Conversation

@ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #6951

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 command region startKey to region keysaccordingly. This is originally proposed as a precondition of the push down optimisation of infomation_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.

  • master (the latest development version)
  • v5.4 (TiDB 5.4 versions)
  • v5.3 (TiDB 5.3 versions)
  • v5.2 (TiDB 5.2 versions)
  • v5.1 (TiDB 5.1 versions)
  • v5.0 (TiDB 5.0 versions)
  • v4.0 (TiDB 4.0 versions)
  • v3.1 (TiDB 3.1 versions)
  • v3.0 (TiDB 3.0 versions)
  • v2.1 (TiDB 2.1 versions)

What is the related PR or file link(s)?

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

IcePigZDB and others added 17 commits May 13, 2022 04:11
ref #tikv/pd/issues/4400

Signed-off-by: IcePigZDB <icepigzdb@gmail.com>

Signed-off-by: IcePigZDB <icepigzdb@gmail.com>
Signed-off-by: IcePigZDB <icepigzdb@gmail.com>
Signed-off-by: IcePigZDB <icepigzdb@gmail.com>
Signed-off-by: IcePigZDB <icepigzdb@gmail.com>
Signed-off-by: IcePigZDB <icepigzdb@gmail.com>
Signed-off-by: IcePigZDB <icepigzdb@gmail.com>
Signed-off-by: IcePigZDB <icepigzdb@gmail.com>
Signed-off-by: IcePigZDB <icepigzdb@gmail.com>
Signed-off-by: IcePigZDB <icepigzdb@gmail.com>
Signed-off-by: IcePigZDB <icepigzdb@gmail.com>
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
Signed-off-by: IcePigZDB <icepigzdb@gmail.com>
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
@ti-chi-bot
Copy link
Member Author

ti-chi-bot commented May 13, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • TomShawn

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Details

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added area/scheduling Indicates that the Issue or PR belongs to the area of scheduling. contribution This PR is from a community contributor. first-time-contributor Indicates that the PR was contributed by an external member and is a first-time contributor. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. type/cherry-pick-for-release-6.0 This PR is cherry-picked to release-6.0 from a source PR. labels May 13, 2022
@ti-chi-bot ti-chi-bot requested a review from shichun-0415 May 13, 2022 04:11
@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label May 13, 2022
@TomShawn
Copy link
Contributor

/merge

@ti-chi-bot
Copy link
Member Author

This pull request has been accepted and is ready to merge.

DetailsCommit hash: da2afaf

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label May 13, 2022
@ti-chi-bot ti-chi-bot merged commit e813809 into pingcap:release-6.0 May 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/scheduling Indicates that the Issue or PR belongs to the area of scheduling. contribution This PR is from a community contributor. first-time-contributor Indicates that the PR was contributed by an external member and is a first-time contributor. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT1 Indicates that a PR has LGTM 1. type/cherry-pick-for-release-6.0 This PR is cherry-picked to release-6.0 from a source PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants