TiCDC emits DML with a DeleteOnly column after changefeed restart
Open
Nobody has claimed this yet.
type/bug
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
What did you do?
Refer https://github.com/pingcap/tiflow/issues/12760
What did you expect to see?
No response
What did you see instead?
None
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)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked issue first, then inspect TiCDC's changefeed restart and schema-state handling; the payload names no source file or test. Reproduce with the supplied TiDB, TiKV, and TiCDC version commands, and verify that a restarted changefeed no longer emits DML containing a DeleteOnly column.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, mysql
- Domain
- data-engineering, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100