deardeng opened a new issue, #43995: URL: https://github.com/apache/doris/issues/43995
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no similar issues. ### Version 2.1.6 ### What's Wrong? 升级流程：1.2.4 -> 2.0.15 ->2.1.6 表应该是很早之前创建的，表参数 in_memory = true了，升级到新版本后，导致动态分区新分区创建都失败。排查发现是这个参数导致的，这里咱们能不能优化下呀，比如这个参数能否强制为false，因为有时候partition没办法创建的话，会导致数据无法入库，等一系列的问题。 ``` 2024-11-04 12:22:03,459 INFO (DynamicPartitionScheduler|51) [PropertyAnalyzer.analyzeDataProperty():274] Can not assign cool down timestamp to HDD storage medium, ignore user setting. 2024-11-04 12:22:03,460 INFO (DynamicPartitionScheduler|51) [DynamicPartitionScheduler.recordCreatePartitionFailedMsg():627] dynamic add partition failed: errCode = 2, detailMessage = errCode = 2, detailMessage = Not support set 'in_memory'='true' now!, db: dim_blockchain, table: doris_dwm_eth_trans_num_180d 2024-11-04 12:22:03,460 WARN (DynamicPartitionScheduler|51) [DynamicPartitionScheduler.executeDynamicPartition():616] has error at org.apache.doris.clone.DynamicPartitionScheduler.executeDynamicPartition(DynamicPartitionScheduler.java:612) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.clone.DynamicPartitionScheduler.runAfterCatalogReady(DynamicPartitionScheduler.java:678) ~[doris-fe.jar:1.2-SNAPSHOT] ``` ### What You Expected? 由旧的1.x版本建表带in_memory = true，升级到2.x版本忽略in_memory 参数，不影响动态分区建分区失败 ### How to Reproduce? _No response_ ### Anything Else? https://github.com/apache/doris/pull/18731 这个pr 将in_memory 废弃的，2.0版本就废弃了这个参数。 https://doris.apache.org/zh-CN/docs/3.0/sql-manual/sql-statements/Data-Definition-Statements/Create/CREATE-TABLE/ 文档上这个也是显示 已废弃 状态 但是[#18731](https://github.com/apache/doris/pull/18731)没有考虑兼容性升级问题 ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
