-
Notifications
You must be signed in to change notification settings - Fork 687
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"split, redefine partitions by using ALTER TABLE statements" is incorrect #5424
Comments
@qw4990 we need to verify and correct the document related to partition table |
/cc @mjonss |
/assign @mjonss |
mjonss
added a commit
to mjonss/docs
that referenced
this issue
Apr 26, 2021
Clarified currently supported partitioning management, and added experimental feature EXCHANGE PARTITION. Fixes pingcap#5424
11 tasks
mjonss
added a commit
to mjonss/docs
that referenced
this issue
Apr 26, 2021
Clarified currently supported partitioning management, and added experimental feature EXCHANGE PARTITION. Fixes pingcap#5424
11 tasks
github-actions bot
pushed a commit
to mjonss/docs
that referenced
this issue
Jul 23, 2021
Clarified currently supported partitioning management, and added experimental feature EXCHANGE PARTITION. Fixes pingcap#5424
ti-chi-bot
pushed a commit
to ti-chi-bot/docs
that referenced
this issue
Jul 23, 2021
Clarified currently supported partitioning management, and added experimental feature EXCHANGE PARTITION. Fixes pingcap#5424
11 tasks
ti-chi-bot
pushed a commit
to ti-chi-bot/docs
that referenced
this issue
Jul 23, 2021
Clarified currently supported partitioning management, and added experimental feature EXCHANGE PARTITION. Fixes pingcap#5424
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://docs.pingcap.com/tidb/stable/partitioned-table#range-partition-management makes this statement:
We do not currently support "split" or "redefine" partition operations, as far as I know and can tell by my testing.
File: /partitioned-table.md
The text was updated successfully, but these errors were encountered: