ddl: let concurrent truncate on the same table depend on the previous one (#40501)#40510
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
|
[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. DetailsReviewer can indicate their review by submitting an approval review. |
|
/cherry-pick-invite |
|
@wjhuang2016 Please accept the invitation then you can push to the cherry-pick pull requests. |
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 130295c |
|
@ti-chi-bot: Your PR was out of date, I have automatically updated it for you. If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. DetailsInstructions 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. |
This is an automated cherry-pick of #40501
Signed-off-by: wjhuang2016 huangwenjun1997@gmail.com
What problem does this PR solve?
Issue Number: close #40484
Problem Summary:
Suppose that we have:
DDL1: truncate table 1.
DDL2: truncate table 2.
Then DDL2 should depend on DDL1.
Since the table id changed, DDL2 is not dependent on DDL1 now.
What is changed and how it works?
For truncate table, its related ID including the old id and new id.
Check List
Tests
As in the issue.
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.