49 lines
1.2 KiB
Markdown
49 lines
1.2 KiB
Markdown
<!-- Thank you for contributing to TiDB!
|
|
|
|
PR Title Format:
|
|
1. pkg [, pkg2, pkg3]: what's changed
|
|
2. *: what's changed
|
|
|
|
-->
|
|
|
|
### What problem does this PR solve?
|
|
|
|
Issue Number: close #xxx <!-- REMOVE this line if no issue to close -->
|
|
|
|
Problem Summary:
|
|
|
|
### What is changed and how it works?
|
|
|
|
Proposal: [xxx](url) <!-- REMOVE this line if not applicable -->
|
|
|
|
What's Changed:
|
|
|
|
How it Works:
|
|
|
|
### Check List <!--REMOVE the items that are not applicable-->
|
|
|
|
Tests <!-- At least one of them must be included. -->
|
|
|
|
- [ ] Unit test
|
|
- [ ] Integration test
|
|
- [ ] Manual test (add detailed scripts or steps below)
|
|
- [ ] No code
|
|
|
|
Side effects
|
|
|
|
- [ ] Performance regression: Consumes more CPU
|
|
- [ ] Performance regression: Consumes more Memory
|
|
- [ ] Breaking backward compatibility
|
|
|
|
Documentation
|
|
|
|
- [ ] Affects user behaviors
|
|
- [ ] Contains syntax changes
|
|
- [ ] Contains variable changes
|
|
- [ ] Contains experimental features
|
|
- [ ] Changes MySQL compatibility
|
|
|
|
### Release note <!-- bugfixes or new feature need a release note -->
|
|
|
|
- <!-- Please write a release note here to describe the change you made when it is released to the users of TiDB. If your PR doesn't involve any change to TiDB(like test enhancements, RFC proposals...), you can write `No release note`. -->
|