ddl: refactor the args for the DDL type of renametable

[joccau]

What problem does this PR solve?

Issue Number: Ref #53930
Ref #54436

Problem Summary:

• Refactor the args in ddl job for the type of renametable

What changed and how does it work?

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

[codecov]

Codecov Report

Attention: Patch coverage is 81.48148% with 15 lines in your changes missing coverage. Please review.

Project coverage is 56.6072%. Comparing base (26443da) to head (36c1356).
Report is 3 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #55959         +/-   ##
=================================================
- Coverage   72.9073%   56.6072%   -16.3002%     
=================================================
  Files          1610       1763        +153     
  Lines        447262     633407     +186145     
=================================================
+ Hits         326087     358554      +32467     
- Misses       101111     250120     +149009     
- Partials      20064      24733       +4669     

Flag	Coverage Δ
integration	39.3100% <59.2592%> (?)
unit	72.0080% <81.4814%> (+0.0033%)	⬆️

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

Components	Coverage Δ
dumpling	52.9567% <ø> (ø)
parser	∅ <ø> (∅)
br	63.0457% <ø> (+17.2470%)	⬆️

[D3Hunter]

link this issue #53930

[joccau]

/test pull-br-integration-test

[tiprow]

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

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test pull-br-integration-test

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.

[joccau]

/test pull-br-integration-test

[tiprow]

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

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test pull-br-integration-test

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.

[joccau]

/test unit-test

[tiprow]

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

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test unit-test

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.

[D3Hunter]

rest lgtm

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: D3Hunter, lance6716

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:

• pkg/ddl/OWNERS [D3Hunter,lance6716]
• pkg/meta/OWNERS [D3Hunter,lance6716]

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]

[LGTM Timeline notifier]

Timeline:

• 2024-09-18 02:54:39.505669634 +0000 UTC m=+1016149.246093574: ☑️ agreed by lance6716.
• 2024-09-18 06:01:22.390623998 +0000 UTC m=+1027352.131047962: ☑️ agreed by D3Hunter.