planner: refactor some code of binding cache

[qw4990]

What problem does this PR solve?

Issue Number: ref #51347

Problem Summary: planner: refactor some code of binding cache

What changed and how does it work?

planner: refactor some code of binding cache

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!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.9159%. Comparing base (40d2481) to head (1494c5e).
Report is 10 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #58532        +/-   ##
================================================
+ Coverage   73.5123%   74.9159%   +1.4036%     
================================================
  Files          1681       1726        +45     
  Lines        464386     472858      +8472     
================================================
+ Hits         341381     354246     +12865     
+ Misses       102136      96329      -5807     
- Partials      20869      22283      +1414     

Flag	Coverage Δ
integration	49.2603% <100.0000%> (?)
unit	72.2768% <100.0000%> (+0.0176%)	⬆️

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

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

[qw4990]

/test check-dev

[tiprow]

@qw4990: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test check-dev

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.

[lance6716]

/hold

free to unhold

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-12-25 07:33:50.289542463 +0000 UTC m=+1633420.378344991: ☑️ agreed by Rustin170506.
• 2024-12-25 08:07:08.616578962 +0000 UTC m=+1635418.705381507: ☑️ agreed by lance6716.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, lance6716, 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 [AilinKid,Rustin170506,lance6716]
• pkg/bindinfo/OWNERS [AilinKid,Rustin170506]
• pkg/domain/OWNERS [lance6716]

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

[qw4990]

/unhold

[qw4990]

/hold

[qw4990]

/unhold

[ti-chi-bot]

@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
idc-jenkins-ci-tidb/check_dev_2	1494c5e	link	unknown	/test check-dev2

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.