Incubating Program: Plan Change Capturer
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 267
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
Project Incubating Request
Plan Change Capturer
Describe the project you want to incubate:
Summary
User story: as a user, I want to ensure there is no performance regression caused by SQL plan changes when updating TiDB.
This tool can detect SQL plan changes between different TiDB versions according to corresponding statistical information and schemas.
This tool is almost done(repo, tutorial), and it's time to make it an incubating project for long-term maintaining.
Estimated Time
30 days
Your RFC/Proposal?
The design doc, and tutorial.
Contributor guide
No contributing guide indexed for this repository
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 with the linked design doc and tutorial, then review the external plan-change-capturer repository to understand the proposed project and its TiDB integration. The issue is complete when the incubation request has a clear decision and a plan for long-term maintenance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100