executor: fix incorrect result when hash agg spill is triggered

[xzhangxian1008]

What problem does this PR solve?

Issue Number: close #55290

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.

Fix the issue that getting incorrect result when hash agg spill is triggered

[tiprow]

Hi @xzhangxian1008. 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.

[xzhangxian1008]

/cc @windtalker @XuHuaiyu

[codecov]

Codecov Report

Attention: Patch coverage is 28.57143% with 20 lines in your changes missing coverage. Please review.

Project coverage is 74.6836%. Comparing base (0a2d5be) to head (ce44d34).
Report is 31 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #55322        +/-   ##
================================================
- Coverage   74.8131%   74.6836%   -0.1295%     
================================================
  Files          1570       1571         +1     
  Lines        364718     450077     +85359     
================================================
+ Hits         272857     336134     +63277     
- Misses        72124      93393     +21269     
- Partials      19737      20550       +813     

Flag	Coverage Δ
integration	48.4269% <14.2857%> (?)
unit	71.8354% <28.5714%> (-1.9135%)	⬇️

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

Components	Coverage Δ
dumpling	52.9567% <ø> (-2.2327%)	⬇️
parser	∅ <ø> (∅)
br	52.4475% <ø> (+4.7567%)	⬆️

[xzhangxian1008]

/hold

[xzhangxian1008]

/cc @XuHuaiyu @windtalker

[xzhangxian1008]

/unhold

[windtalker]

lgtm

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: windtalker, 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 [XuHuaiyu,windtalker]

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-08-09 11:15:30.64894972 +0000 UTC m=+609860.516048804: ☑️ agreed by XuHuaiyu.
• 2024-08-12 03:34:08.167561837 +0000 UTC m=+152532.871031496: ☑️ agreed by windtalker.

[tiprow]

@xzhangxian1008: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
fast_test_tiprow	3ea6e38	link	true	/test fast_test_tiprow

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[ti-chi-bot]

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