Mryange opened a new pull request, #63588:
URL: https://github.com/apache/doris/pull/63588

   ### What problem does this PR solve?
   
   Problem Summary:
   
   A local exchange source without a limit can currently trust eos even when 
unread data is still buffered in the exchanger. In that case the pipeline may 
finish with fewer output rows than input rows and the failure is hidden behind 
a normal end-of-stream. Root cause: the source path did not validate exchanger 
state after eos, and AdaptivePassthroughExchanger also has a tmp block path 
outside the normal queue state. This change adds a post-eos residual-data check 
for the no-limit source path, reports detailed queue and buffered-block 
diagnostics when unread data remains, and adds unit tests that cover both queue 
residuals and adaptive passthrough tmp-block residuals.
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test <!-- At least one of them must be included. -->
       - [ ] Regression test
       - [ ] Unit Test
       - [ ] Manual test (add detailed scripts or steps below)
       - [ ] No need to test or manual test. Explain why:
           - [ ] This is a refactor/code format and no logic has been changed.
           - [ ] Previous test can cover this change.
           - [ ] No code files have been changed.
           - [ ] Other reason <!-- Add your reason?  -->
   
   - Behavior changed:
       - [ ] No.
       - [ ] Yes. <!-- Explain the behavior change -->
   
   - Does this need documentation?
       - [ ] No.
       - [ ] Yes. <!-- Add document PR link here. eg: 
https://github.com/apache/doris-website/pull/1214 -->
   
   ### Check List (For Reviewer who merge this PR)
   
   - [ ] Confirm the release note
   - [ ] Confirm test cases
   - [ ] Confirm document
   - [ ] Add branch pick label <!-- Add branch pick label that this PR should 
merge into -->
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to