Uh oh!
There was an error while loading. Please reload this page.
[fix](split)Fixed the bug that batch mode split could not query data in multiple be scenarios. - #46218
Merged
Merged
Conversation
…in multiple be scenarios.
hello-stephen
commented
Dec 31, 2024
Contributor
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
hubgeter
commented
Dec 31, 2024
ContributorAuthor
run buildall |
doris-robot
commented
Dec 31, 2024
TPC-H: Total hot run time: 32775 ms |
doris-robot
commented
Dec 31, 2024
TPC-DS: Total hot run time: 190504 ms |
doris-robot
commented
Dec 31, 2024
ClickBench: Total hot run time: 31.48 s |
Jibing-Li
approved these changes
Dec 31, 2024
Contributor
PR approved by at least one committer and no changes requested. |
Contributor
PR approved by anyone and no changes requested. |
morningman
approved these changes
Dec 31, 2024
github-actionsBot
pushed a commit
that referenced
this pull request
Dec 31, 2024
…in multiple be scenarios. (#46218) ### What problem does this PR solve? Problem Summary: In multiple be scenarios, batch mode split sometimes could not query data. The reason is that the estimated `numApproximateSplits()` may be relatively small, and the value after dividing the current number of be may be 0. As a result, the split will not be distributed to be, and the query result will be empty. We need to take the max of the value after division and 1.
github-actionsBot
pushed a commit
that referenced
this pull request
Dec 31, 2024
…in multiple be scenarios. (#46218) ### What problem does this PR solve? Problem Summary: In multiple be scenarios, batch mode split sometimes could not query data. The reason is that the estimated `numApproximateSplits()` may be relatively small, and the value after dividing the current number of be may be 0. As a result, the split will not be distributed to be, and the query result will be empty. We need to take the max of the value after division and 1.
GoGoWen pushed a commit
to GoGoWen/incubator-doris
that referenced
this pull request
Sep 26, 2025
…in multiple be scenarios. apache#46218 (apache#46227)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
Problem Summary:
In multiple be scenarios, batch mode split sometimes could not query data.
The reason is that the estimated
numApproximateSplits()may be relatively small, and the value after dividing the current number of be may be 0. As a result, the split will not be distributed to be, and the query result will be empty.We need to take the max of the value after division and 1.
Followup #45148
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)