planner: introduce a new fuzzy binding cache

[qw4990]

What problem does this PR solve?

Issue Number: ref #51347

Problem Summary: planner: introduce a new fuzzy binding cache

What changed and how does it work?

Mainly it's refactoring. Introduce a new cache between the BindingHandler and the BindingCache, where we can implement some advanced binding features like 'fuzzy matching', 'auto binding loading if cache miss', etc...

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/test-infra repository.

[codecov]

Codecov Report

Merging #51401 (cd03ea0) into master (026ad96) will increase coverage by 2.6454%.
Report is 16 commits behind head on master.
The diff coverage is 93.6170%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #51401        +/-   ##
================================================
+ Coverage   70.6330%   73.2785%   +2.6454%     
================================================
  Files          1461       1462         +1     
  Lines        434877     441256      +6379     
================================================
+ Hits         307167     323346     +16179     
+ Misses       108414      98062     -10352     
- Partials      19296      19848       +552     

Flag	Coverage Δ
integration	49.4241% <90.4255%> (?)
unit	70.7431% <93.6170%> (+0.3202%)	⬆️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	51.4552% <ø> (+5.6152%)	⬆️

[hawkingrei]

/ok-to-test

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-02-29 08:00:22.434140974 +0000 UTC m=+1121711.181764085: ☑️ agreed by hawkingrei.
• 2024-02-29 08:44:33.199397253 +0000 UTC m=+1124361.947020349: ☑️ agreed by hi-rustin.

[qw4990]

/test unit-test

[tiprow]

@qw4990: 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/test-infra repository.

[qw4990]

/test unit-test

[tiprow]

@qw4990: 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/test-infra repository.

[hawkingrei]

/retest

[hawkingrei]

/test all

[elsa0520]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elsa0520, hawkingrei, hi-rustin

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 [elsa0520,hawkingrei,hi-rustin]

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