support sequence replicate
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 291
- Forks
- 131
- Avg merge
- 5m
- Merged PRs (30d)
- 2
Description
Feature Request
Is your feature request related to a problem? Please describe:
ref https://github.com/orgs/pingcap/projects/5#card-33682988
https://github.com/pingcap/tidb/pull/14954
Describe the feature you'd like:
Describe alternatives you've considered:
normal replicate thinks about sequence.
it will just abort the replication now, and noway to recover.
Teachability, Documentation, Adoption, Migration Strategy:
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 reviewing the referenced project card and pull request #14954, since no source files or tests are named in the issue. Clarify how sequence replication should behave and identify the existing replication entry points from that work. Done should mean normal replication handles sequences without aborting and leaves a recoverable state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100