[fix](partial update) fix partial update always failed after create rollup/MV #58003
Conversation
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
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 36065 ms |
TPC-DS: Total hot run time: 188865 ms |
ClickBench: Total hot run time: 27.77 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
Contributor
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
sollhui
force-pushed
the
partial_update_after_rollup
branch
from
b498314 to
a06434a
Compare
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 34501 ms |
TPC-DS: Total hot run time: 188429 ms |
ClickBench: Total hot run time: 27.68 s |
Contributor
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
Contributor
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
sollhui
force-pushed
the
partial_update_after_rollup
branch
from
a06434a to
61f2e78
Compare
Contributor
Author
|
run buildall |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
TPC-H: Total hot run time: 34843 ms |
TPC-DS: Total hot run time: 187259 ms |
ClickBench: Total hot run time: 27.53 s |
sollhui
force-pushed
the
partial_update_after_rollup
branch
from
61f2e78 to
ef516f6
Compare
Contributor
Author
|
run buildall |
sollhui
force-pushed
the
partial_update_after_rollup
branch
2 times, most recently
from
af4d894 to
37f4d5b
Compare
sollhui
force-pushed
the
partial_update_after_rollup
branch
from
37f4d5b to
d286182
Compare
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 35451 ms |
Contributor
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 34086 ms |
TPC-DS: Total hot run time: 186435 ms |
ClickBench: Total hot run time: 27.56 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
Contributor
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
Contributor
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
Contributor
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
github-actions
bot
added
the
approved
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
bobhan1
approved these changes
Nov 26, 2025
github-actions bot
pushed a commit
that referenced
this pull request
Nov 26, 2025
…ollup/MV (#58003) ### What problem does this PR solve? Create a rollup: ``` ALTER TABLE mow_table ADD ROLLUP rollup1(event_date, event_time, user_id, country, update_time) ``` update table after create rollup with column(city) do not exist in rollup: ``` UPDATE mow_table SET city = "beijing" WHERE user_id = 2000 ``` BE node will core dump(#57934 avoid core dump, but still always fail)
sollhui
added a commit
to sollhui/doris
that referenced
this pull request
Dec 1, 2025
…ollup/MV (apache#58003) Create a rollup: ``` ALTER TABLE mow_table ADD ROLLUP rollup1(event_date, event_time, user_id, country, update_time) ``` update table after create rollup with column(city) do not exist in rollup: ``` UPDATE mow_table SET city = "beijing" WHERE user_id = 2000 ``` BE node will core dump(apache#57934 avoid core dump, but still always fail)
sollhui
added a commit
to sollhui/doris
that referenced
this pull request
Dec 1, 2025
…ollup/MV (apache#58003) Create a rollup: ``` ALTER TABLE mow_table ADD ROLLUP rollup1(event_date, event_time, user_id, country, update_time) ``` update table after create rollup with column(city) do not exist in rollup: ``` UPDATE mow_table SET city = "beijing" WHERE user_id = 2000 ``` BE node will core dump(apache#57934 avoid core dump, but still always fail)
nagisa-kunhah
pushed a commit
to nagisa-kunhah/doris
that referenced
this pull request
Dec 14, 2025
…ollup/MV (apache#58003) ### What problem does this PR solve? Create a rollup: ``` ALTER TABLE mow_table ADD ROLLUP rollup1(event_date, event_time, user_id, country, update_time) ``` update table after create rollup with column(city) do not exist in rollup: ``` UPDATE mow_table SET city = "beijing" WHERE user_id = 2000 ``` BE node will core dump(apache#57934 avoid core dump, but still always fail)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
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?
Create a rollup:
update table after create rollup with column(city) do not exist in rollup:
BE node will core dump(#57934 avoid core dump, but still always fail)
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)