executor: fix incorrect results when there is an IndexLookUp under the inner side of an Apply (#19496) #19508
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
/run-all-tests |
ti-srebot
added
component/executor
Priority/P0
|
/run-all-tests |
|
LGTM |
ti-srebot
added
status/LGT2
|
/merge |
|
Sorry @zz-jason, you don't have permission to trigger auto merge event on this branch. |
|
/merge |
ti-srebot
added
the
status/can-merge
|
/run-all-tests |
|
@ti-srebot merge failed. |
|
/run-unit-test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cherry-pick #19496 to release-4.0
What problem does this PR solve?
Issue Number: close #19372
Problem Summary: executor: fix incorrect results when there is an IndexLookUp under the inner side of an Apply
What is changed and how it works?
When an
IndexLookUpis under the inner side of anApply, it may be invoked multiple times, but inIndexLookUp.Close(), the fieldresultCurris not cleared up, so in the next round of invocation, some stale rows may be returned because of this logic.Check List
Tests
Release note