No mentioning of limitations of EXCHANGE PARTITION when it comes to Index IDs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 617
- Forks
- 724
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 223
Description
Change Request
Please answer the following questions before submitting your issue. Thanks!
-
Describe what you find is inappropriate or missing in the existing docs.
In https://github.com/pingcap/tidb/issues/50906 there is an issue for EXCHANGE PARTITION, when the table structures looks the same, but internally they have different index ids. -
Describe your suggestion or addition.
Add a paragraph about EXCHANGE PARTITION and table structures, including the workaroundCREATE TABLE tnp LIKE partitioned_table; alter table tnp remove partitioning;to get exact the same indexes etc. -
Provide some reference materials (such as documents and websites) if you could.
https://docs.pingcap.com/tidb/stable/partitioned-table#partition-management
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
Open the partition-management section at the linked TiDB documentation page and review the referenced TiDB issue about EXCHANGE PARTITION and differing index IDs. Document the limitation and the stated CREATE TABLE LIKE plus REMOVE PARTITIONING workaround; the section should clearly explain when matching visible structures are insufficient.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100