ddl_notifier: get complete table info after unmarshal SchemaChangeEvent

[fzzf678]

What problem does this PR solve?

Issue Number: ref #55722

Problem Summary:

What changed and how does it work?

tidb/pkg/meta/model/table.go

Line 196 in ba5823b

DBID int64 `json:"-"`

The DBID is ignored when marshaling TableInfo, so the DBID is always 0 after we unmarshal the SchemaChangeEvent, the follow-up event process logic may be failed by this. So we get the complete table info by table id before process event.

Check List

Tests

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

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[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 assign gmhdbjd for approval. 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:

• pkg/ddl/OWNERS

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

[tiprow]

Hi @fzzf678. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[codecov]

Codecov Report

Attention: Patch coverage is 68.42105% with 6 lines in your changes missing coverage. Please review.

Project coverage is 57.0588%. Comparing base (ba5823b) to head (0f70377).
Report is 5 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #56796         +/-   ##
=================================================
- Coverage   73.3727%   57.0588%   -16.3140%     
=================================================
  Files          1635       1785        +150     
  Lines        452770     639629     +186859     
=================================================
+ Hits         332210     364965      +32755     
- Misses       100208     249571     +149363     
- Partials      20352      25093       +4741     

Flag	Coverage Δ
integration	39.3214% <68.4210%> (?)

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

Components	Coverage Δ
dumpling	52.9478% <ø> (ø)
parser	∅ <ø> (∅)
br	63.1157% <ø> (+17.0926%)	⬆️

[ti-chi-bot]

@fzzf678: 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
pull-unit-test-ddlv1	0f70377	link	true	/test pull-unit-test-ddlv1
idc-jenkins-ci-tidb/unit-test	0f70377	link	true	/test unit-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/test-infra repository. I understand the commands that are listed here.

[fzzf678]

replace by #56803