pingcap / pingcap/tidb-operator
TiCDC supports writing to remote storage directly
Open
Nobody has claimed this yet.
area/tools
status/help-wanted
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
Is your feature request related to a problem? Please describe:
https://github.com/pingcap/ticdc/pull/826 supports writing logs to S3.
Describe the feature you'd like:
Describe alternatives you've considered:
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
The request references pingcap/ticdc pull request 826 as prior work supporting S3 log writing, but names no files, tests, or entry points in this repository. Start by reviewing that referenced change and the TiCDC integration in this project. Done would require a defined, tested path for TiCDC to write logs directly to remote storage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100