planner: fix agg push down rule mistake order by item inside agg function

[AilinKid]

What problem does this PR solve?

Issue Number: close #49986

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.

planner: fix agg push down rule mistake order by item inside agg function

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

[AilinKid]

/check-issue-triage-complete

[AilinKid]

/check-issue-triage-complete

[codecov]

Codecov Report

Merging #50002 (fe09892) into master (5f79a7c) will decrease coverage by 3.2494%.
Report is 13 commits behind head on master.
The diff coverage is 100.0000%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #50002        +/-   ##
================================================
- Coverage   71.9074%   68.6581%   -3.2494%     
================================================
  Files          1437       1440         +3     
  Lines        345665     409009     +63344     
================================================
+ Hits         248559     280818     +32259     
- Misses        76879     109195     +32316     
+ Partials      20227      18996      -1231     

Flag	Coverage Δ
integration	43.9168% <100.0000%> (?)
unit	71.9074% <ø> (-0.0001%)	⬇️

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

Components	Coverage Δ
dumpling	56.3129% <ø> (ø)
parser	∅ <ø> (∅)
br	43.4338% <ø> (-7.8812%)	⬇️

[AilinKid]

/test check-dev2

[tiprow]

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

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [hawkingrei,qw4990]

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-01-03 05:42:26.956835454 +0000 UTC m=+2235637.994062372: ☑️ agreed by qw4990.
• 2024-01-03 06:26:27.485348723 +0000 UTC m=+2238278.522575650: ☑️ agreed by hawkingrei.

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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