planner: refactor a few code of plan cache

[qw4990]

What problem does this PR solve?

Issue Number: ref #54057

Problem Summary: planner: refactor a few code of plan cache

What changed and how does it work?

Add table dirty flags into the plan cache key

No regression

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.

[hawkingrei]

Other LGTM

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

• OWNERS [AilinKid,hawkingrei]
• pkg/planner/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-07-04 07:47:30.673589817 +0000 UTC m=+1483377.159078648: ☑️ agreed by AilinKid.
• 2024-07-04 07:56:00.009788567 +0000 UTC m=+1483886.495277399: ☑️ agreed by hawkingrei.

[qw4990]

/test pull-mysql-client-test

[tiprow]

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

In response to this:

/test pull-mysql-client-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.

[qw4990]

/retest

[codecov]

Codecov Report

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

Project coverage is 56.2057%. Comparing base (be16d49) to head (fa961da).
Report is 8 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #54442         +/-   ##
=================================================
- Coverage   74.7851%   56.2057%   -18.5794%     
=================================================
  Files          1536       1659        +123     
  Lines        361822     610055     +248233     
=================================================
+ Hits         270589     342886      +72297     
- Misses        71592     243810     +172218     
- Partials      19641      23359       +3718     

Flag	Coverage Δ
integration	37.1842% <86.3013%> (?)
unit	71.9369% <84.9315%> (-1.7607%)	⬇️

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

Components	Coverage Δ
dumpling	52.9656% <ø> (-2.2339%)	⬇️
parser	∅ <ø> (∅)
br	52.6856% <ø> (+4.7701%)	⬆️

[qw4990]

/retest

[tiprow]

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

In response to this:

/retest

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.

[qw4990]

/test unit-test

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