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

Fix DDL split events #960

Merged
merged 10 commits into from
Feb 6, 2025
Merged

Fix DDL split events #960

merged 10 commits into from
Feb 6, 2025

Conversation

wk989898
Copy link
Collaborator

What problem does this PR solve?

Issue Number: close #xxx

What is changed and how it works?

  1. use parse to split queries
  2. split renaming tables

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No code

Questions

Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?

Release note

Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.

If you don't think this PR needs a release note then fill it with `None`.

@ti-chi-bot ti-chi-bot bot added do-not-merge/needs-linked-issue release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 27, 2025
pkg/common/event/ddl_event.go Outdated Show resolved Hide resolved
pkg/common/event/ddl_event.go Outdated Show resolved Hide resolved
pkg/common/event/ddl_event.go Outdated Show resolved Hide resolved
pkg/common/event/ddl_event.go Outdated Show resolved Hide resolved
Copy link

ti-chi-bot bot commented Feb 6, 2025

[FORMAT CHECKER NOTIFICATION]

Notice: To remove the do-not-merge/needs-linked-issue label, please provide the linked issue number on one line in the PR body, for example: Issue Number: close #123 or Issue Number: ref #456.

📖 For more info, you can check the "Contribute Code" section in the development guide.

@wk989898 wk989898 requested a review from lidezhu February 6, 2025 08:15
@ti-chi-bot ti-chi-bot bot added the lgtm label Feb 6, 2025
Copy link

ti-chi-bot bot commented Feb 6, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lidezhu

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

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link

ti-chi-bot bot commented Feb 6, 2025

[LGTM Timeline notifier]

Timeline:

  • 2025-02-06 09:04:50.160905985 +0000 UTC m=+348961.693317968: ☑️ agreed by lidezhu.

@ti-chi-bot ti-chi-bot bot added the approved label Feb 6, 2025
@ti-chi-bot ti-chi-bot bot merged commit 93cc0d6 into pingcap:master Feb 6, 2025
10 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants