ddl: fix rename table across database

[lidezhu]

What problem does this PR solve?

Issue Number: close #11963

What is changed and how it works?

Construct a rename table query which contains database name and table name in the ddl event.

Check List

Tests

• 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

Fixed the issue that rename table ddl cannot be synchronized in some cases.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from lidezhu, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 50.8839%. Comparing base (91902aa) to head (7e5e90d).
Report is 46 commits behind head on master.

✅ All tests successful. No failed tests found.

Additional details and impacted files

Components	Coverage Δ
cdc	∅ <ø> (∅)
dm	50.0815% <ø> (+1.1919%)	⬆️
engine	53.2449% <ø> (∅)

Flag	Coverage Δ
unit	50.8839% <ø> (-2.7395%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

@@               Coverage Diff                @@
##             master     #11964        +/-   ##
================================================
- Coverage   55.2634%   50.8839%   -4.3795%     
================================================
  Files          1004        484       -520     
  Lines        137733      69857     -67876     
================================================
- Hits          76116      35546     -40570     
+ Misses        56048      31549     -24499     
+ Partials       5569       2762      -2807     

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[lidezhu]

/hold

[lidezhu]

/unhold

[wk989898]

Does it impact rename multiple tables?

[lidezhu]

No. Rename tables has it's unique way get these info.

[asddongmen]

/test all

[asddongmen]

/verify

[asddongmen]

/test verify

[ti-chi-bot]

@asddongmen: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test pull-cdc-integration-kafka-test

/test pull-cdc-integration-mysql-test

/test pull-cdc-integration-pulsar-test

/test pull-cdc-integration-storage-test

/test pull-dm-compatibility-test

/test pull-dm-integration-test

/test pull-syncdiff-integration-test

/test pull-verify

/test wip-pull-build

/test wip-pull-check

/test wip-pull-unit-test-cdc

/test wip-pull-unit-test-dm

/test wip-pull-unit-test-engine

Use /test all to run the following jobs that were automatically triggered:

pingcap/tiflow/ghpr_verify

pingcap/tiflow/pull_cdc_integration_kafka_test

pingcap/tiflow/pull_cdc_integration_pulsar_test

pingcap/tiflow/pull_cdc_integration_storage_test

pingcap/tiflow/pull_cdc_integration_test

pingcap/tiflow/pull_dm_compatibility_test

pingcap/tiflow/pull_dm_integration_test

pingcap/tiflow/pull_syncdiff_integration_test

In response to this:

/test verify

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 kubernetes-sigs/prow repository.

[lidezhu]

/retest

[ti-chi-bot]

@lidezhu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
jenkins-ticdc/verify	c99eece	link	true	/test verify
pull-verify	7e5e90d	link	true	/test pull-verify
pull-cdc-integration-pulsar-test	7e5e90d	link	true	/test pull-cdc-integration-pulsar-test
pull-cdc-integration-mysql-test	7e5e90d	link	true	/test pull-cdc-integration-mysql-test
pull-cdc-integration-kafka-test	7e5e90d	link	true	/test pull-cdc-integration-kafka-test
pull-cdc-integration-storage-test	7e5e90d	link	true	/test pull-cdc-integration-storage-test

Full PR test history. Your PR dashboard.

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.