Not call abortMPPGather when mpp task met error (#7969) #8005
+518
−0
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.
This is an automated cherry-pick of #7969
What problem does this PR solve?
Issue Number: ref #7177
Problem Summary: When MPPTask has 'always false' filter, it will close receiver before receiving all data. It will cause 'false positive' errors. And when there are other MPPTasks which consumes data from 'always false' MPPTasks in the same
tiflash node, abortMPPGather may convert 'false positive' errors to 'real' errors. Here is a specific example: #7177 (comment)
What is changed and how it works?
Check List
Tests
Manually test tpcds q44, which contains 'always false' filter.
Side effects
Documentation
Release note