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

filter(ticdc): fix incorrect event filter with "rename" DDLs #11956

Merged
merged 7 commits into from
Jan 3, 2025

Conversation

wk989898
Copy link
Collaborator

@wk989898 wk989898 commented Dec 31, 2024

What problem does this PR solve?

Issue Number: close #11946

What is changed and how it works?

Event Filter wrongly uses the current table info with "rename" DDLs and It should use the previous table info to filter events.

Check List

Tests

  • Unit test
  • Integration test

Questions

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

Release note

Fix incorrect event filter with "rename table" DDLs

@ti-chi-bot ti-chi-bot bot added do-not-merge/needs-triage-completed 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 Dec 31, 2024
@wk989898
Copy link
Collaborator Author

wk989898 commented Jan 2, 2025

/retest

@kennytm
Copy link
Contributor

kennytm commented Jan 2, 2025

does it work if the DDL renamed multiple tables (e.g. rename a1 to b1, a2 to b2, b3 to a3;)?

@wk989898
Copy link
Collaborator Author

wk989898 commented Jan 2, 2025

does it work if the DDL renamed multiple tables (e.g. rename a1 to b1, a2 to b2, b3 to a3;)?

Yes, you can check the integration test.

@wk989898
Copy link
Collaborator Author

wk989898 commented Jan 2, 2025

/retest

Copy link
Contributor

@kennytm kennytm left a comment

Choose a reason for hiding this comment

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

rest lgtm

pkg/filter/sql_event_filter.go Outdated Show resolved Hide resolved
@ti-chi-bot ti-chi-bot bot added approved needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Jan 2, 2025
Copy link
Contributor

ti-chi-bot bot commented Jan 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: asddongmen, kennytm

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

@ti-chi-bot ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Jan 3, 2025
Copy link
Contributor

ti-chi-bot bot commented Jan 3, 2025

[LGTM Timeline notifier]

Timeline:

  • 2025-01-02 16:08:53.599311028 +0000 UTC m=+625868.955315569: ☑️ agreed by kennytm.
  • 2025-01-03 03:02:08.028117112 +0000 UTC m=+665063.384121649: ☑️ agreed by asddongmen.

Co-authored-by: kennytm <kennytm@gmail.com>
@wk989898
Copy link
Collaborator Author

wk989898 commented Jan 3, 2025

/check-issue-triage-complete

@ti-chi-bot ti-chi-bot bot merged commit 1e1f271 into pingcap:master Jan 3, 2025
26 checks passed
@wk989898
Copy link
Collaborator Author

wk989898 commented Jan 3, 2025

/cherry-pick release-8.5
/cherry-pick release-8.1
/cherry-pick release-7.5

@ti-chi-bot
Copy link
Member

@wk989898: new pull request created to branch release-7.5: #11967.

In response to this:

/cherry-pick release-8.5
/cherry-pick release-8.1
/cherry-pick release-7.5

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.

ti-chi-bot pushed a commit to ti-chi-bot/tiflow that referenced this pull request Jan 3, 2025
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot
Copy link
Member

@wk989898: new pull request created to branch release-8.1: #11968.

In response to this:

/cherry-pick release-8.5
/cherry-pick release-8.1
/cherry-pick release-7.5

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.

@ti-chi-bot
Copy link
Member

@wk989898: new pull request created to branch release-8.5: #11969.

In response to this:

/cherry-pick release-8.5
/cherry-pick release-8.1
/cherry-pick release-7.5

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.

@kennytm
Copy link
Contributor

kennytm commented Jan 3, 2025

i haven't tested but i think the issue affected 6.5 and 7.1 too

@wk989898
Copy link
Collaborator Author

wk989898 commented Jan 4, 2025

/cherry-pick release-7.1
/cherry-pick release-6.5
/cherry-pick release-6.1

ti-chi-bot pushed a commit to ti-chi-bot/tiflow that referenced this pull request Jan 4, 2025
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot
Copy link
Member

@wk989898: new pull request created to branch release-6.1: #11972.

In response to this:

/cherry-pick release-7.1
/cherry-pick release-6.5
/cherry-pick release-6.1

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.

ti-chi-bot pushed a commit to ti-chi-bot/tiflow that referenced this pull request Jan 4, 2025
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot
Copy link
Member

@wk989898: new pull request created to branch release-6.5: #11973.

In response to this:

/cherry-pick release-7.1
/cherry-pick release-6.5
/cherry-pick release-6.1

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.

ti-chi-bot pushed a commit to ti-chi-bot/tiflow that referenced this pull request Jan 4, 2025
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot
Copy link
Member

@wk989898: new pull request created to branch release-7.1: #11974.

In response to this:

/cherry-pick release-7.1
/cherry-pick release-6.5
/cherry-pick release-6.1

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.

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
4 participants