You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
Version
doris-2.1.6
What's Wrong?
In a cluster that only has SSD storage, creating a table not set storage medium, create table succeeds, but the output of the SHOW CREATE TABLE command incorrectly shows the storage medium as HDD, and execute create table t4 like t3 will failed
What You Expected?
create table t4 like t3 success
show create table t3 show t3 storage medium is ssd
How to Reproduce?
Deploy Doris with the disk medium set to SSD
Create a table using SQL create table t3(a bigint, b int) engine=olap uniqueKEY(a) distributed by hash (a) buckets 1 properties( "replication_num" = "1");
show create table t3 , it will display table medium HHD
create table t4 like t3 will failed
Anything Else?
HOW to fix:
When calling olapTable.setStorageMedium, also store the isSpecialStorageMedium flag
Add isSpecialStorageMedium to the properties stored in TableProperty
In the attribute table for ALTER TABLE, set the isSpecialStorageMedium to true
at last, add a docker regression case for test it
Search before asking
Version
doris-2.1.6
What's Wrong?
In a cluster that only has SSD storage, creating a table not set storage medium, create table succeeds, but the output of the
SHOW CREATE TABLE
command incorrectly shows the storage medium as HDD, and executecreate table t4 like t3
will failedWhat You Expected?
create table t4 like t3
successshow create table t3
show t3 storage medium is ssdHow to Reproduce?
create table t3(a bigint, b int) engine=olap uniqueKEY(a) distributed by hash (a) buckets 1 properties( "replication_num" = "1");
show create table t3
, it will display table medium HHDcreate table t4 like t3
will failedAnything Else?
HOW to fix:
at last, add a docker regression case for test it
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: