planner: don't change the multi stage count's final return type

[AilinKid]

What problem does this PR solve?

Issue Number: close #48643

Problem Summary:

What is changed and how it works?

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.

planner: don't change the multi stage count's final return type

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

[codecov]

Codecov Report

Merging #48675 (4273067) into master (9cf638f) will decrease coverage by 17.4896%.
Report is 24 commits behind head on master.
The diff coverage is 100.0000%.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #48675         +/-   ##
=================================================
- Coverage   71.0083%   53.5188%   -17.4896%     
=================================================
  Files          1367       1585        +218     
  Lines        404865     596878     +192013     
=================================================
+ Hits         287488     319442      +31954     
- Misses        97372     254910     +157538     
- Partials      20005      22526       +2521     

Flag	Coverage Δ
integration	35.0936% <0.0000%> (?)
unit	70.9835% <100.0000%> (-0.0248%)	⬇️

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

Components	Coverage Δ
dumpling	53.9663% <ø> (ø)
parser	∅ <ø> (∅)
br	55.4329% <ø> (+2.3560%)	⬆️

[AilinKid]

/retest

[AilinKid]

/ok-to-test

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-11-24 07:27:14.857992362 +0000 UTC m=+562063.523218556: ☑️ agreed by qw4990.
• 2023-11-24 12:04:54.67954482 +0000 UTC m=+578723.344771017: ☑️ agreed by winoros.

[AilinKid]

/retest

[AilinKid]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, qw4990, winoros, XuHuaiyu

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,XuHuaiyu,qw4990,winoros]
• pkg/expression/OWNERS [XuHuaiyu]

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]

In response to a cherrypick label: new pull request created to branch release-6.1: #48930.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #48931.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #48932.

[AilinKid]

/run-cherry-picker

[AilinKid]

/run cherry-picker

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #49036.