TiCDC did not correctly use the primary key as the where clause for the Delete statement.

[asddongmen]

What did you do?

I use TiCDC to synchronize a table with one primary key (consisting of two columns of int values) and a non-null unique index (consisting of 3 columns). I observed from the logs that the where statement of the Delete statement generated by TiCDC did not correctly use the primary key as an execution condition.

What did you expect to see?

TiCDC uses primary key to generate the where clause of delete statements.

What did you see instead?

as above.

Versions of the cluster

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

(paste TiDB cluster version here)

Upstream TiKV version (execute tikv-server --version):

(paste TiKV version here)

TiCDC version (execute cdc version):

(paste TiCDC version here)