Uh oh!
There was an error while loading. Please reload this page.
[fix](sequence column) fix update fail on nereids planner - #28031
Conversation
3a558bb to
028ba1bComparezhannngchen
commented
Dec 5, 2023
run buildall |
doris-robot
commented
Dec 5, 2023
TPC-H test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
doris-robot
commented
Dec 5, 2023
(From new machine)TeamCity pipeline, clickbench performance test result: |
| if (!haveInputSeqCol && !isPartialUpdate) { | ||
| if (!haveInputSeqCol && !isPartialUpdate && ( | ||
| boundSink.getDmlCommandType() != DMLCommandType.UPDATE | ||
| && boundSink.getDmlCommandType() != DMLCommandType.DELETE)) { |
There was a problem hiding this comment.
could we add a help function in DMLCommandType for easy use?
There was a problem hiding this comment.
sounds not necessary? only 4 types
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
028ba1b to
3a7963aComparezhannngchen
commented
Dec 13, 2023
run buildall |
zhannngchen
commented
Dec 13, 2023
run buildall |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
doris-robot
commented
Dec 13, 2023
TPC-H test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
zhannngchen
commented
Dec 13, 2023
run clickbench-new |
doris-robot
commented
Dec 13, 2023
TPC-H test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
doris-robot
commented
Dec 13, 2023
(From new machine)TeamCity pipeline, clickbench performance test result: |
doris-robot
commented
Dec 13, 2023
TPC-H test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
1. if we set enable_fallback_to_original_planner to false, the UPDATE sql in regression case test_unique_table_sequence will fail due to:“Table test_uniq_sequence has sequence column, need to specify the sequence column”,The bug is introduced by [fix](sequence column) insert into should require sequence column in all scenario apache#27780 2. fix insert fail in transaction mode, which is introduced by [refactor](Nereids) let insert into compatible with legacy planner apache#27947 3. add cases with session variable enable_fallback_to_original_planner false
pr apache#28105 and apache#28031 merging conflict caused this case to fail.
1. if we set enable_fallback_to_original_planner to false, the UPDATE sql in regression case test_unique_table_sequence will fail due to:“Table test_uniq_sequence has sequence column, need to specify the sequence column”,The bug is introduced by [fix](sequence column) insert into should require sequence column in all scenario apache#27780 2. fix insert fail in transaction mode, which is introduced by [refactor](Nereids) let insert into compatible with legacy planner apache#27947 3. add cases with session variable enable_fallback_to_original_planner false
pr apache#28105 and apache#28031 merging conflict caused this case to fail.
1. if we set enable_fallback_to_original_planner to false, the UPDATE sql in regression case test_unique_table_sequence will fail due to:“Table test_uniq_sequence has sequence column, need to specify the sequence column”,The bug is introduced by [fix](sequence column) insert into should require sequence column in all scenario apache#27780 2. fix insert fail in transaction mode, which is introduced by [refactor](Nereids) let insert into compatible with legacy planner apache#27947 3. add cases with session variable enable_fallback_to_original_planner false
pr apache#28105 and apache#28031 merging conflict caused this case to fail.
Proposed changes
Issue Number: close #xxx
if we set
enable_fallback_to_original_plannerto false, theUPDATEsql in regression casetest_unique_table_sequencewill fail due to:The bug is introduced by [fix](sequence column) insert into should require sequence column in all scenario #27780
fix insert fail in transaction mode, which is introduced by [refactor](Nereids) let insert into compatible with legacy planner #27947
add cases with session variable
enable_fallback_to_original_plannerfalseFurther comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...