0AyanamiRei opened a new pull request, #64762:
URL: https://github.com/apache/doris/pull/64762

   ### What problem does this PR solve?
   
   Issue Number: None
   
   Related PR: None
   
   Problem Summary: Stream load status reporting could dereference a missing 
stream load context, ignore the status carried by 
PReportStreamLoadStatusRequest, and race with normal completion by writing the 
same load status promise multiple times. This changes stream load status 
completion to go through a single set_load_status_once helper, propagates the 
reported RPC status to stream load waiters, and returns an error when the load 
id is unknown.
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test <!-- At least one of them must be included. -->
       - [ ] Regression test
       - [x] Unit Test
           - ./run-be-ut.sh --run 
--filter=StreamLoadContextTest.*:InternalServiceStreamLoadStatusTest.* -j60
       - [x] Manual test (add detailed scripts or steps below)
           - ./build.sh --be -j60
           - build-support/check-format.sh
           - git diff --check
           - build-support/run-clang-tidy.sh --build-dir be/build_ASAN (failed 
due to local clang-tidy PCH/AST error: malformed block record in AST file)
       - [ ] 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.
       - [x] Yes. Stream load status reporting now returns an error for unknown 
load ids and propagates reported stream load failure status.
   
   - Does this need documentation?
       - [x] No.
       - [ ] Yes. <!-- Add document PR link here. eg: 
https://github.com/apache/doris-website/pull/1214 -->
   


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