DDL | Description |
Create a Table | 1. Automatic Table Creation: When a new table appears in the monitored source database, the target will automatically create a table with the same structure and fields. 2. Ignore Changes: The target ignores the DDL change messages from the source. The target and logs do not respond or issue any alerts. 3. Log Alarms: The target will only receive DDL change messages and log the message contents without triggering any table creation operations. 4. Task Error: The target receives DDL change messages and continuously restarts the task. During the restart process, the task logs errors and data write exceptions occur. |
Add a Column | 1. Auto-add Columns: When a new column appears in the monitored source table, the target will automatically create a column with the same name. 2. Ignore Changes: The target ignores the DDL change messages from the source. The target and logs do not respond or issue any alerts. 3. Log Alarms: The target will only receive DDL change messages and log the message contents without triggering any column creation operations. 4. Task Error: The target receives DDL change messages and continuously restarts the task. During the restart process, the task logs errors and data write exceptions occur. |
Delete a Column | 1. Automatic deletion of columns: When a column is deleted in the monitored source table, the target will automatically delete the column with the same name. 2. Ignore Changes: The target ignores the DDL change messages from the source. The target and logs do not respond or issue any alerts. 3. Log Alarms: The target will only receive DDL change messages and log the message contents. This policy does not trigger any column deletion operations. 4. Task Error: The target receives DDL change messages and continuously restarts the task. During the restart process, the task logs errors and data write exceptions occur. |
Rename a column | 1. Automatic renaming of columns: When a column name changes in the monitored source table, the target will automatically rename the column. 2. Ignore Changes: The target ignores the DDL change messages from the source. The target and logs do not respond or issue any alerts. 3. Log Alarms: The target will only receive DDL change messages and log the message contents. This policy does not trigger any column renaming operations. 4. Task Error: The target receives DDL change messages and continuously restarts the task. During the restart process, the task logs errors and data write exceptions occur. |
Column type modification | 1. Automatic modification of column types: When there is a column type change in the monitored database on the source end, such as field length change or adding a comment, the target end will automatically make the corresponding change. 2. Ignore Changes: The target ignores the DDL change messages from the source. The target and logs do not respond or issue any alerts. 3. Log Alerts: The target will only receive DDL change messages and log the message content. This policy does not trigger column type modification operations. 4. Task Error: The target receives DDL change messages and continuously restarts the task. During the restart process, the task logs errors and data write exceptions occur. |
Delete a Table | 1. Ignore Changes: The target ignores the DDL change messages from the source. The target and logs do not respond or issue any alerts. 2. Log Alerts: The target will only receive DDL change messages and log the message content. This policy does not trigger Delete Table/Rename Table/Empty Table operations. 3. Task Error: The target receives DDL change messages and continuously restarts the task. During the restart process, the task logs errors and data write exceptions occur. |
Rename a Table | |
Empty Table | |
Type | Read (Source side) | | | | | | | | | | |
| DML | | | DDL | | | | | | | |
| Insert | Delete | Updating | Add a Column | Delete a Column | Rename a column | Column type modification | Add Table | Rename a Table | Delete a Table | Empty Table |
MySQL | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
TDSQL-C MySQL | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
TDSQL MySQL | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Oracle | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | Yes |
SQL Server | Yes | Yes | Yes | No | No | No | No | No | No | No | No |
PostgreSQL | Yes | Yes | Yes | Yes | Yes | No | Yes | Yes | No | Yes | Yes |
OceanBase | Yes | Yes | Yes | No | No | No | No | No | No | No | No |
Kafka | NA | NA | NA | NA | NA | NA | NA | NA | NA | NA | NA |
Type | Write (Target end) | | | | | | | | | | |
| DML | | | DDL | | | | | | | |
| Insert | Delete | Updating | Add a Column | Delete a Column | Rename a column | Column type modification | Add Table | Rename a Table | Delete a Table | Empty Table |
DLC | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No |
Iceberg | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No |
Doris | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No |
StarRocks | Yes | Yes | Yes | Yes | Yes | No | Yes | Yes | No | No | No |
TChouse-P | Yes | Yes | Yes | Yes | No | No | No | Yes | No | No | No |
Elasticsearch | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | No | No | No |
Hive | Yes | No | No | No | No | No | No | No | No | No | No |
Kafka | NA | NA | NA | NA | NA | NA | NA | NA | NA | NA | NA |
RENAME TABLE tbl_name TO new_tbl_name
CREATE TABLE [IF NOT EXISTS] tbl_name (create_definition,...) CREATE TABLE new_tbl LIKE orig_tbl; CREATE TABLE new_tbl AS SELECT * FROM orig_tbl;
ALTER TABLE t1 MODIFY b INT NOT NULL; ALTER TABLE t1 CHANGE b a INT NOT NULL;
ALTER TABLE table_name ADD new_column_name column_definition [ FIRST | AFTER column_name ];
Alter table t2 DROP [COLUMN] col_name
truncate table a;
drop table a;
Was this page helpful?