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

   ### What problem does this PR solve?
   
   Issue Number: None
   
   Related PR: None
   
   Problem Summary:
   
   When a Broker Load fragment reports `DATA_QUALITY_ERROR` together with a 
tracking URL, Coordinator updates the failure status first. The failure path 
cancels the Coordinator and releases the completion latch before the report 
handler stores the tracking URL. `LoadLoadingTask` may therefore wake up, 
snapshot a null URL, and persist it into the final Load Job state even though 
FE subsequently logs the valid URL.
   
   This change publishes the tracking URL before failure status handling can 
release waiters:
   
   - Legacy Coordinator stores the URL before calling `updateStatus()`.
   - Nereids LoadProcessor uses a pre-status diagnostics hook to publish the 
URL before `updateStatusIfOk()`.
   - Deterministic unit tests verify that URL publication happens before 
cancellation in both paths.
   
   The patch intentionally does not change load counters, first-error messages, 
Cloud retry behavior, or downstream persistence.
   
   ### Release note
   
   Fix `SHOW LOAD` potentially returning a null URL for failed Broker Load jobs 
when an error-log URL was reported.
   
   ### Check List (For Author)
   
   - Test:
     - [x] Unit Test
       - Added deterministic ordering tests for legacy and Nereids report paths.
       - Not run locally; CI will be requested with `run buildall`.
     - [ ] Regression test
     - [ ] Manual test
   - Behavior changed:
     - [x] Yes. Failed Broker Load reports publish the tracking URL before 
waking load-task waiters.
     - [ ] No.
   - Does this need documentation:
     - [ ] Yes.
     - [x] No.


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