Skip to content
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

ddl: change drop partition and truncate partition's job args to support multi partition id array (#18419) #18930

Merged
merged 1 commit into from
Aug 3, 2020

Conversation

ti-srebot
Copy link
Contributor

cherry-pick #18419 to release-4.0


Signed-off-by: AilinKid [email protected]

What problem does this PR solve?

it is prepared for cancel add multi partition action which is in mid state

Problem Summary: change drop partition and truncate partition's job args to support multi partition id array

What is changed and how it works?

What's Changed:
1: change drop partition and truncate partition's job args to multi id array
2: support ddl worker to handle these two action and add ids to delete range table.

Check List

Tests

  • Unit test
  • Integration test

Side effects

  • Breaking backward compatibility

Release note

  • change drop partition and truncate partition's job args to support multi partition id array
  • Notice: This is a in-compatible change and we can not:
    1: rolling upgrade the cluster during the drop partition DDL operation
    2: degrade to old tidb if the model data has been written and the DDL operation is not finished

@ti-srebot
Copy link
Contributor Author

/run-all-tests

@AilinKid
Copy link
Contributor

AilinKid commented Aug 3, 2020

/run-all-tests

Copy link
Contributor

@crazycs520 crazycs520 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-srebot ti-srebot added the status/LGT1 Indicates that a PR has LGTM 1. label Aug 3, 2020
Copy link
Contributor

@djshow832 djshow832 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-srebot ti-srebot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Aug 3, 2020
@AilinKid
Copy link
Contributor

AilinKid commented Aug 3, 2020

/run-check_dev

@lance6716
Copy link
Contributor

LGTM

@ti-srebot
Copy link
Contributor Author

@lance6716,Thanks for your review. However, LGTM is restricted to Reviewers or higher roles.See the corresponding SIG page for more information. Related SIGs: ddl(slack).

@bb7133
Copy link
Member

bb7133 commented Aug 3, 2020

/merge

@ti-srebot ti-srebot added the status/can-merge Indicates a PR has been approved by a committer. label Aug 3, 2020
@ti-srebot
Copy link
Contributor Author

/run-all-tests

@ti-srebot ti-srebot added status/LGT3 The PR has already had 3 LGTM. and removed status/LGT2 Indicates that a PR has LGTM 2. labels Aug 3, 2020
@ti-srebot ti-srebot merged commit 64e2a23 into pingcap:release-4.0 Aug 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compatibility-breaker Violation of forwards/backwards compatibility in a design-time piece. sig/sql-infra SIG: SQL Infra status/can-merge Indicates a PR has been approved by a committer. status/LGT3 The PR has already had 3 LGTM. type/4.0-cherry-pick
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants