TiCDC treats all rows in a ineligible table (no PK/UK) as conflicting, forcing it to be replicated with a single worker only
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
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
Start by reading the referenced issue pingcap/tiflow#12296, since the issue body provides no local files, tests, entry points, or reproduction steps. Determine the expected handling of rows in tables without a primary or unique key and define a reproducible test before implementation; the current issue does not specify what completion looks like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100