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

   ### What problem does this PR solve?
   
   Problem Summary:
   
   MaxCompute dynamic-partition writes need each partition's rows to be 
contiguous in one writer stream, so the connector sink requested a partition 
shuffle plus a local sort. It used `MustLocalSortOrderSpec` for that, which the 
enforcer reads as "sort locally BEFORE distributing" and therefore appends a 
global sort: an extra merging exchange after the partition shuffle. Under 
local-channel backpressure that merging receiver can wait forever on a sender 
blocked by another full receiver queue, hanging `INSERT INTO <dynamic-partition 
table>` until the client-side socket times out.
   
   This PR requests a plain `OrderSpec` on top of the hash distribution 
instead, so the plan becomes `distribution -> local sort` (no global sort, no 
merging exchange) while keeping the same writer-local grouping contract. The 
SPI javadoc, the unit tests, and the MaxCompute write cases (explain shape: 
`VSORT` before `VEXCHANGE`, no `VMERGING-EXCHANGE`) are updated accordingly.
   
   ### Release note
   
   Fix intermittent hangs when writing dynamic partitions to MaxCompute.
   
   ### Check List (For Author)
   
   - Test
       - [x] Regression test
       - [x] 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
   
   - Behavior changed:
       - [ ] No.
       - [x] Yes.
   
   - Does this need documentation?
       - [x] No.
       - [ ] Yes.
   
   ### Check List (For Reviewer who merge this PR)
   
   - [ ] Confirm the release note
   - [ ] Confirm test cases
   - [ ] Confirm document
   - [ ] Add branch pick label


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