planner: fix panic error when subquery + always true predicate in where clause

[elsa0520]

What problem does this PR solve?

Issue Number: close #46962

Problem Summary:

What changed and how does it work?

Skip the partial agg mode check in the key_build_info when the agg function is empty.

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 @elsa0520. 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]

/ok-to-test

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

• pkg/planner/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-05-24 03:38:35.112406835 +0000 UTC m=+2402068.869542403: ☑️ agreed by qw4990.
• 2024-05-24 03:39:54.232819579 +0000 UTC m=+2402147.989955152: ☑️ agreed by hawkingrei.

[codecov]

Codecov Report

Attention: Patch coverage is 80.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 73.8754%. Comparing base (acdb6f5) to head (247c90d).
Report is 1228 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #53525        +/-   ##
================================================
+ Coverage   72.4943%   73.8754%   +1.3810%     
================================================
  Files          1493       1524        +31     
  Lines        429359     444807     +15448     
================================================
+ Hits         311261     328603     +17342     
+ Misses        98889      96044      -2845     
- Partials      19209      20160       +951     

Flag	Coverage Δ
integration	49.3204% <80.0000%> (?)
unit	71.3383% <80.0000%> (-0.0585%)	⬇️

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

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

In response to a cherrypick label: new pull request could not be created: failed to create pull request against pingcap/tidb#release-7.1 from head ti-chi-bot:cherry-pick-53525-to-release-7.1: the GitHub API request returns a 403 error: {"message":"You have exceeded a secondary rate limit and have been temporarily blocked from content creation. Please retry your request again later. If you reach out to GitHub Support for help, please include the request ID ACA6:3F108B:1B83AEF:33D976F:671F4684 and timestamp 2024-10-28 08:08:36 UTC.","documentation_url":"https://docs.github.com/rest/overview/rate-limits-for-the-rest-api#about-secondary-rate-limits","status":"403"}

[elsa0520]

/cherry-pick release-7.1

[ti-chi-bot]

@elsa0520: new pull request created to branch release-7.1: #57102.

In response to this:

/cherry-pick release-7.1

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 ti-community-infra/tichi repository.