handle-error skip throw error

[lddlww]

handle-error skip throw error

[lance6716]

as described "only support to handle ddl error", handle-error can't skip transaction. Skipping transaction will cause data loss so we don't plan to do it.

[lddlww]

so, what can i do to solve error？

[lddlww]

» query-status gamelab01-task01
{
    "result": true,
    "msg": "",
    "sources": [
        {
            "result": true,
            "msg": "",
            "sourceStatus": {
                "source": "gamelab01",
                "worker": "worker2",
                "result": null,
                "relayStatus": null
            },
            "subTaskStatus": [
                {
                    "name": "gamelab01-task01",
                    "stage": "Paused",
                    "unit": "Sync",
                    "result": {
                        "isCanceled": false,
                        "errors": [
                            {
                                "ErrCode": 36027,
                                "ErrClass": "sync-unit",
                                "ErrScope": "internal",
                                "ErrLevel": "high",
                                "Message": "startLocation: [position: (, 0), gtid-set: ], endLocation: [position: (mysql-bin.000009, 299330026), gtid-set: 915a5f85-8fd9-4820-b112-2d296273ece1:1-806952,9c656ea1-9999-11ea-9641-74867af4110d:1]: gen insert sqls failed, schema: gamelab, table: g_orders: Column count doesn't match value count: 30 (columns) vs 31 (values)",
                                "RawCause": "",
                                "Workaround": "Please check the log files to see if a related DDL has been skipped, and you could use `operate-schema` to get and set the table structure."
                            }
                        ],
                        "detail": null
                    },
                    "unresolvedDDLLockID": "",
                    "sync": {
                        "totalEvents": "0",
                        "totalTps": "0",
                        "recentTps": "0",
                        "masterBinlog": "(mysql-bin.000009, 299760347)",
                        "masterBinlogGtid": "915a5f85-8fd9-4820-b112-2d296273ece1:1-807832,9c656ea1-9999-11ea-9641-74867af4110d:1",
                        "syncerBinlog": "(mysql-bin.000009, 299329480)",
                        "syncerBinlogGtid": "915a5f85-8fd9-4820-b112-2d296273ece1:1-806951,9c656ea1-9999-11ea-9641-74867af4110d:1",
                        "blockingDDLs": [
                        ],
                        "unresolvedGroups": [
                        ],
                        "synced": false,
                        "binlogType": "remote"
                    }
                }
            ]
        }
    ]
}

i want to skip this error，because tidb g_orders table structure is the same as mysql

[lance6716]

as said in message, “you could use operate-schema to get and set the table structure”

https://docs.pingcap.com/zh/tidb-data-migration/stable/manage-schema#%E5%91%BD%E4%BB%A4%E4%BB%8B%E7%BB%8D

[lddlww]

thanks ， i issue operate-schema set -s gamelab01 gamelab01-task01 -d gamelab -t g_orders g_orders.sql to modify dm internal table structure, then the dm syncer is running again now