HappenLee opened a new pull request, #63574:
URL: https://github.com/apache/doris/pull/63574
### What problem does this PR solve?
Issue Number: None
Related PR: None
Problem Summary: ExchangeSinkBuffer still carried a legacy
_send_multi_blocks flag and mixed single-block and multi-block request
assembly. This made the sending logic harder to reason about and left a
compatibility branch in the sender. The change unifies request assembly around
the blocks repeated field and uses exchange_multi_blocks_byte_size > 0 as the
only switch; when the option is unset or non-positive, each RPC carries a
single block.
### Release note
None
### Check List (For Author)
- Test: No need to test (logic-only refactor; verified diff and request flow)
- No need to test
- Behavior changed: Yes (unset/non-positive exchange_multi_blocks_byte_size
now always uses single-block sending)
- Does this need documentation: No
### What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
### 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]
