CREATE VIEW will interrupt replication task

[lance6716]

What did you do?

start a task

MySQL [mydb]> create view t10 as select * from t1;

What did you expect to see?

task is not interrupted

What did you see instead?

                    "name": "test",
                    "stage": "Paused",
                    "unit": "Sync",
                    "result": {
                        "isCanceled": false,
                        "errors": [
                            {
                                "ErrCode": 11007,
                                "ErrClass": "functional",
                                "ErrScope": "internal",
                                "ErrLevel": "high",
                                "Message": "startLocation: [position: (mysql-bin.000001, 1794), gtid-set: 2c43df5b-5eea-11ec-aff5-0242ac110002:1-6], endLocation: [position: (mysql-bin.000001, 2009), gtid-set: 2c43df5b-5eea-11ec-aff5-0242ac110002:1-7], origin SQL: [CREATE ALGORITHM=UNDEFINED DEFINER=`root`@`%` SQL SECURITY DEFINER VIEW `t10` AS select * from t1]: unknown type ddl \u0026{ddlNode:{stmtNode:{node:{text:CREATE ALGORITHM=UNDEFINED DEFINER=`root`@`%!`(MISSING) SQL SECURITY DEFINER VIEW `t10` AS select * from t1 offset:0}}} OrReplace:false ViewName:0xc005fa4a50 Cols:[] Select:0xc0004a2ff0 SchemaCols:[] Algorithm:0 Definer:root@%!S(MISSING)ecurity:0 CheckOption:1}",
                                "RawCause": "",
                                "Workaround": "Please manually handle it using dmctl (skipping the DDL statement or replacing the DDL statement with a specified DDL statement). For details, see https://docs.pingcap.com/tidb-data-migration/stable/handle-failed-sql-statements"
                            }

Versions of the cluster

DM version (run dmctl -V or dm-worker -V or dm-master -V):

v5.3.0

Upstream MySQL/MariaDB server version:

(paste upstream MySQL/MariaDB server version here)

Downstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):

(paste TiDB cluster version here)

How did you deploy DM: tiup or manually?

(leave TiUP or manually here)

Other interesting information (system version, hardware config, etc):

>
>

current status of DM cluster (execute query-status <task-name> in dmctl)

(paste current status of DM cluster here)

[lance6716]

this is caused by SplitDDL didn't recognize this type of DDL thus throws error. And we didn't use regexp to filter that error.

tiflow/dm/syncer/syncer.go

Line 2423 in cdb4f64

qec.splitDDLs, err = parserpkg.SplitDDL(stmt, qec.ddlSchema)