【详述】：
SDM做集群间同步，源端跟目标端都是存算一体架构，源端3.0.9，目标端：3.1.11，在源端进行创建表，且仅有一个分区表，然后再删除这个分区表，想问下这是SDM的本身的机制？还是BUG？
– 表结构如下：
CREATE TABLE dwm_order (
yyyymm varchar(10) NULL COMMENT “月份”,
date_id date NULL COMMENT “日期”,
order_id varchar(100) NULL COMMENT “主订单ID”,
sub_order_id varchar(100) NULL COMMENT “子订单ID”,
mapping_order_no varchar(100) NULL COMMENT “第三方订单号”,
etl_time datetime NULL COMMENT “etl抽取时间”
) ENGINE=OLAP
DUPLICATE KEY(yyyymm, date_id, order_id, sub_order_id, mapping_order_no)
PARTITION BY RANGE(date_id)
(PARTITION p202405 VALUES [(“2024-05-01”), (“2024-06-01”)))
DISTRIBUTED BY HASH(order_id, sub_order_id) BUCKETS 1
PROPERTIES (
“replication_num” = “1”,
“in_memory” = “false”,
“enable_persistent_index” = “false”,
“replicated_storage” = “true”,
“compression” = “LZ4”
);
– 删除分区命令如下：
ALTER TABLE dm.dwm_order DROP PARTITION IF EXISTS p202405 FORCE
– 查看SDM日志如下：
24/05/09 17:17:28 WARN [meta-handler] sendDropPartitionJob(ClusterMetaKeeper.java:216):
Skip the DROP PARTITION that only exists on the target cluster: ALTER TABLE dm.dwm_order DROP PARTITION IF EXISTS p202405 FORCE
24/05/09 17:20:28 WARN [meta-handler] sendDropPartitionJob(ClusterMetaKeeper.java:216):
Skip the DROP PARTITION that only exists on the target cluster: ALTER TABLE dm.dwm_order DROP PARTITION IF EXISTS p202405 FORCE