-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fix](schema change) Fix can't do reorder column schema change for MOW table and duplicate key table #37067
Conversation
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
run buildall |
TPC-H: Total hot run time: 39870 ms
|
TPC-DS: Total hot run time: 172284 ms
|
ClickBench: Total hot run time: 30.46 s
|
LGTM |
PR approved by anyone and no changes requested. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
PR approved by at least one committer and no changes requested. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
run p0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
427d676
to
8505246
Compare
run buildall |
TPC-H: Total hot run time: 40197 ms
|
TPC-DS: Total hot run time: 173890 ms
|
ClickBench: Total hot run time: 30.4 s
|
regression-test/suites/schema_change/test_schema_change_datev2_with_delete.groovy
Outdated
Show resolved
Hide resolved
ee047b0
to
f0a7810
Compare
run buildall |
TPC-H: Total hot run time: 39556 ms
|
TPC-DS: Total hot run time: 172920 ms
|
ClickBench: Total hot run time: 30.24 s
|
run external |
f0a7810
to
fb24d58
Compare
run buildall |
TPC-H: Total hot run time: 40679 ms
|
TPC-DS: Total hot run time: 173581 ms
|
ClickBench: Total hot run time: 30.93 s
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…W table and duplicate key table (#37067) ## Proposed changes 1. set column's field `isAggregationTypeImplicit` correctly for mow table and duplicate key table to let `SchemaChangeHandler::createJob` can recognize that the schema change is a column reorder case. 2. remove useless test cases `test_schema_change_datev2_with_delete`, `test_dup_keys_schema_change_datev2`. These two cases wanted to test schema change from `datev1`/`datetimev1` to `datev2`/`datetimev2`. But the default type of columns created as `date`/`datetime` are already `datev2`/`datetimev2` now. Thest test cases should have met error "Nothing is changed. please check your alter stmt." when doris enable `datev2`/`datetimev2` by default but it didn't because `isAggregationTypeImplicit` is wrongly set for duplicate table column.
…schema change for MOW table and duplicate key table apache#37067" (apache#37515) ## Proposed changes picks apache#37067
Proposed changes
isAggregationTypeImplicit
correctly for mow table and duplicate key table to letSchemaChangeHandler::createJob
can recognize that the schema change is a column reorder case.test_schema_change_datev2_with_delete
,test_dup_keys_schema_change_datev2
. These two cases wanted to test schema change fromdatev1
/datetimev1
todatev2
/datetimev2
. But the default type of columns created asdate
/datetime
are alreadydatev2
/datetimev2
now. Thest test cases should have met error "Nothing is changed. please check your alter stmt." when doris enabledatev2
/datetimev2
by default but it didn't becauseisAggregationTypeImplicit
is wrongly set for duplicate table column.branch-2.1-pick: #37226
branch-2.0-pick: #37515