-
Notifications
You must be signed in to change notification settings - Fork 289
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
Support ALTER TABLE t REORGANIZE PARTITION #8114
Conversation
[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. |
Could you please fix the failed unit tests and add a |
Hi @asddongmen, I have added such test as well. Could you please review it now? |
@asddongmen @zhaoxinyu @tangenta PTAL, I have updated the patch and included the requested test. |
@@ -26,4 +26,7 @@ ALTER TABLE t1 EXCHANGE PARTITION p3 WITH TABLE t2; | |||
insert into t2 values (100),(101),(102),(103),(104),(105); /*these values will be replicated to in downstream t2*/ | |||
insert into t1 values (25),(29); /*these values will be replicated to in downstream t1.p3*/ | |||
|
|||
ALTER TABLE t1 REORGANIZE PARTITION p0,p2 INTO (PARTITION p0 VALUES LESS THAN (5), PARTITION p1 VALUES LESS THAN (10), PARTITION p2 VALUES LESS THAN (21)); | |||
ALTER TABLE t1 REORGANIZE PARTITION p2,p3,p4 INTO (PARTITION p2 VALUES LESS THAN (20), PARTITION p3 VALUES LESS THAN (26), PARTITION p4 VALUES LESS THAN (35), PARTITION pMax VALUES LESS THAN (MAXVALUE)); | |||
|
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.
Please add some insert querys below line 29 and line 30 to examine TiCDC can replicate data correctly after these DDL. thanks!
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.
@asddongmen I have added some dml after each of the two DML statements.
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.
thank you ~! LGTM
/merge |
This pull request has been accepted and is ready to merge. Commit hash: bd30743
|
@mjonss: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests
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. 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. |
/retest |
/run-verify |
/run-engine-integration-test |
/run-kafka-integration-test |
/run-MySQL-integration |
/run-verify |
This reverts commit 129d619.
What problem does this PR solve?
Issue Number: close #8113
What is changed and how it works?
Adding
timodel.ActionReorganizePartition
to theallowDDLList
and include it forupdatePartition
inDoHandleDDL
.Check List
Tests
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note