pingcap / pingcap/tidb-operator
Enable backup schedule customize the startTime of compacts
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
Now, the backup schedule only support the compact from the startTs (if upgraded from the older edition, then the checkpoint).
We should allow user to customize the startTime of compact, to enable them to skip some time interval they don't need. (maybe too old or something)
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
No files or tests are named. Start by tracing how backup schedules choose the compact startTs or upgrade checkpoint, then identify the schedule configuration and controller paths involved. Define how a user-provided startTime skips earlier intervals, and verify that the configured behavior is applied consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100