planner: refactor some code related to binding

[qw4990]

What problem does this PR solve?

Issue Number: ref #51347

Problem Summary: planner: refactor some code related to binding

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

[tiprow]

Hi @qw4990. 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.

[Rustin170506]

Thanks!

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-02-06 08:02:21.190079266 +0000 UTC m=+345212.722491266: ☑️ agreed by hawkingrei.
• 2025-02-06 08:08:57.167951981 +0000 UTC m=+345608.700363974: ☑️ agreed by Rustin170506.

[tiprow]

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

Test name	Commit	Details	Required	Rerun command
fast_test_tiprow	5de8745	link	true	/test fast_test_tiprow

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.

[codecov]

Codecov Report

Attention: Patch coverage is 80.00000% with 5 lines in your changes missing coverage. Please review.

Project coverage is 73.4881%. Comparing base (444c38f) to head (8495ed6).
Report is 1 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #59272        +/-   ##
================================================
+ Coverage   73.0574%   73.4881%   +0.4306%     
================================================
  Files          1689       1689                
  Lines        466990     467032        +42     
================================================
+ Hits         341171     343213      +2042     
+ Misses       104844     102857      -1987     
+ Partials      20975      20962        -13     

Flag	Coverage Δ
integration	42.8096% <72.0000%> (?)
unit	72.2747% <80.0000%> (+0.0166%)	⬆️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	45.4258% <ø> (+0.0172%)	⬆️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benmeadowcroft, hawkingrei, Rustin170506

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:

• OWNERS [Rustin170506,hawkingrei]
• pkg/bindinfo/OWNERS [Rustin170506,hawkingrei]
• pkg/planner/OWNERS [Rustin170506,hawkingrei]
• pkg/session/OWNERS [benmeadowcroft]

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