planner: some code clean after all logical op are migrated

[AilinKid]

What problem does this PR solve?

Issue Number: ref #51664, ref #52714

Problem Summary:

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 @AilinKid. 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.

[zimulala]

Why remove these assignments？

[AilinKid]

after logicalop is migrated, we can call the func directly rather than a func pointer

[codecov]

Codecov Report

Attention: Patch coverage is 94.30894% with 7 lines in your changes missing coverage. Please review.

Project coverage is 75.8523%. Comparing base (0bcbf8a) to head (54e6107).
Report is 38 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #56426        +/-   ##
================================================
+ Coverage   73.3819%   75.8523%   +2.4704%     
================================================
  Files          1623       1626         +3     
  Lines        447910     457494      +9584     
================================================
+ Hits         328685     347020     +18335     
+ Misses        99082      89884      -9198     
- Partials      20143      20590       +447     

Flag	Coverage Δ
integration	49.7437% <91.8699%> (?)
unit	73.1345% <91.0569%> (+0.6678%)	⬆️

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

Components	Coverage Δ
dumpling	52.9478% <ø> (ø)
parser	∅ <ø> (∅)
br	52.0099% <ø> (+6.4936%)	⬆️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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/planner/OWNERS [hawkingrei,winoros]

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-10-09 08:07:51.014567703 +0000 UTC m=+1033426.434780716: ☑️ agreed by hawkingrei.
• 2024-10-09 16:47:16.99546724 +0000 UTC m=+1064592.415680252: ☑️ agreed by winoros.

[hawkingrei]

/retest

[AilinKid]

/test mysql-test

[tiprow]

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

In response to this:

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

[AilinKid]

/ok-to-test