Uh oh!
There was an error while loading. Please reload this page.
branch-3.1: [Fix](flexible partial update) Fix some problems in flexible partial update #41701 #53765 - #53518
Conversation
bobhan1
commented
Jul 18, 2025
run buildall |
Thearas
commented
Jul 18, 2025
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
hello-stephen
commented
Jul 18, 2025
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
doris-robot
commented
Jul 18, 2025
TPC-H: Total hot run time: 40246 ms |
doris-robot
commented
Jul 18, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
doris-robot
commented
Jul 18, 2025
TPC-DS: Total hot run time: 191318 ms |
doris-robot
commented
Jul 18, 2025
ClickBench: Total hot run time: 29.25 s |
hello-stephen
commented
Jul 18, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
08ed2e0 to
33ec910Comparebobhan1
commented
Jul 21, 2025
run buildall |
hello-stephen
commented
Jul 21, 2025
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
doris-robot
commented
Jul 21, 2025
TPC-H: Total hot run time: 40549 ms |
doris-robot
commented
Jul 21, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
33ec910 to
ae4ca33Comparebobhan1
commented
Jul 22, 2025
run buildall |
hello-stephen
commented
Jul 22, 2025
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Jul 22, 2025
FE UT Coverage ReportIncrement line coverage |
doris-robot
commented
Jul 22, 2025
TPC-H: Total hot run time: 32616 ms |
hello-stephen
commented
Jul 22, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
doris-robot
commented
Jul 22, 2025
TPC-DS: Total hot run time: 196702 ms |
doris-robot
commented
Jul 22, 2025
ClickBench: Total hot run time: 29.33 s |
…update (apache#41701) 1. Fix incorrect result when there are insert after delete for same key in one load. In flexible partial update, if there is an insert after a delete on the same key in one batch, the final result will be always delete that row in table, which is incorrect. The reason is that when doing aggregation for rows with same keys in memtable, we treat delete sign column as an ordinary column. So if there is a row with delete sign in that batch, the final aggregated row will always have a delete sign and any insert on the same key after it will be lost. In the above situation, we should keep those rows and don't merge them when doing aggregation in memtable. When flush the memtable to segment, we should first apply the semantic of delete if exists and then insert the row after it. 2. fix flexible partial update don't use row store column to read data 3. Fix flexible partial update incorrect read index when resolving conflict in publish phase 4. add some default value cases and fix on update current timestamp 5. fix publish phase alignment problem when table has sequence column and the rowset to read has multi segments. 6. add some publish alignment case when table has sequence column 7. ~revert apache#25346, we use the sequence value in flush phase as its final value and will not do alignment in publish phase if the partial update load doesn't specified sequence column.~ 8. fix auto-increment column value is wrongly updated when it's not specified. 9. Fix the problem that the value of sequence column may decrease. 10. Only read seq col and seq map col when the previous row is deleted in partial update and flexible partial update when doing alignment. 11. Fix the value of auto-increment column is not consistent between replicas.
505cf7b to
6d7bd63Comparebobhan1
commented
Jul 23, 2025
run buildall |
hello-stephen
commented
Jul 23, 2025
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
bobhan1
commented
Jul 23, 2025
run buildall |
hello-stephen
commented
Jul 23, 2025
FE UT Coverage ReportIncrement line coverage |
doris-robot
commented
Jul 23, 2025
TPC-DS: Total hot run time: 197230 ms |
doris-robot
commented
Jul 23, 2025
ClickBench: Total hot run time: 29.15 s |
hello-stephen
commented
Jul 23, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
bobhan1
commented
Jul 23, 2025
run cloud_p0 |
bobhan1
commented
Jul 23, 2025
run nonConcurrent |
bobhan1
commented
Jul 23, 2025
run feut |
bobhan1
commented
Jul 23, 2025
run cloud_p0 |
hello-stephen
commented
Jul 23, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Jul 23, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
bobhan1
commented
Jul 24, 2025
run feut |
bobhan1
commented
Jul 24, 2025
run cloud_p0 |
bobhan1
commented
Jul 24, 2025
run buildall |
hello-stephen
commented
Jul 24, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Jul 24, 2025
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
bobhan1
commented
Jul 24, 2025
run beut |
bobhan1
commented
Jul 24, 2025
run performance |
doris-robot
commented
Jul 24, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Jul 24, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Jul 24, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
1 similar comment
hello-stephen
commented
Jul 24, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
bobhan1
commented
Jul 24, 2025
run performance |
1 similar comment
bobhan1
commented
Jul 24, 2025
run performance |
doris-robot
commented
Jul 24, 2025
TPC-H: Total hot run time: 32980 ms |
doris-robot
commented
Jul 24, 2025
TPC-DS: Total hot run time: 190399 ms |
doris-robot
commented
Jul 24, 2025
ClickBench: Total hot run time: 28.91 s |
Uh oh!
There was an error while loading. Please reload this page.
pick #41701 and #53765