planner: rename fuzzyBinding to crossDBBinding in SPM

[qw4990]

What problem does this PR solve?

Issue Number: ref #51347

Problem Summary: planner: rename fuzzyBinding to crossDBBinding in SPM

What changed and how does it work?

planner: rename fuzzyBinding to crossDBBinding in SPM

no logical change, just refactoring

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.

[codecov]

Codecov Report

Attention: Patch coverage is 96.51163% with 3 lines in your changes missing coverage. Please review.

Project coverage is 73.6101%. Comparing base (659e3e7) to head (95b8f7f).
Report is 6 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #58402        +/-   ##
================================================
+ Coverage   73.1844%   73.6101%   +0.4256%     
================================================
  Files          1680       1680                
  Lines        463034     463326       +292     
================================================
+ Hits         338869     341055      +2186     
+ Misses       103374     101434      -1940     
- Partials      20791      20837        +46     

Flag	Coverage Δ
integration	43.1357% <94.1860%> (?)
unit	72.2860% <96.5116%> (-0.0363%)	⬇️

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

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

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, hawkingrei

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/bindinfo/OWNERS [AilinKid,hawkingrei]

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-12-19 03:41:37.320999655 +0000 UTC m=+1101087.409802200: ☑️ agreed by hawkingrei.
• 2024-12-19 03:54:01.971477174 +0000 UTC m=+1101832.060279719: ☑️ agreed by AilinKid.

[qw4990]

/test unit-test

[qw4990]

/test check-dev2

[tiprow]

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

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.

[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-dev2

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.