content_image/763051.jpg
-> PARTITIONS 4; ERROR 1503 (HY000): A PRIMARY KEY must include all columns in the table’s partitioning function 

However, this statement using the id  column for the partitioning column is valid, as shown here: 

mysql> ALTER TABLE np_pk -> PARTITION BY HASH(id) -> PARTITIONS 4; Query OK, 0 rows affected (0.11 sec) Records: 0 Duplicates: 0 Warnings: 0 

In the case of np_pk , the only column that may be used as part of a partitioning expression is id ; if you wish to partition this table using any other column or columns in the partitioning expression, you must first modify the table, either by adding the desired column or columns to the primary key, or by dropping the primary key altogether. 

## 24.6.2 Partitioning Limitations Relating to Storage Engines 

In MySQL 8.0, partitioning support is not actually provided by the MySQL Server, but rather by a table storage engine’s own or native partitioning handler. In MySQL 8.0, only the InnoDB  storage engine provides a native partitioning handler. This means that partitioned tables cannot be created using any other storage engine. 

<img src='content_image/763051.jpg'>

## Note 

MySQL Cluster’s NDB  storage engine also provides native partitioning support, but is not currently supported in MySQL 8.0. 

ALTER TABLE ... OPTIMIZE PARTITION  does not work correctly with partitioned tables that use InnoDB . Use ALTER TABLE ... REBUILD PARTITION  and ALTER TABLE ... ANALYZE PARTITION , instead, for such tables. For more information, see Section 13.1.9.1, “ALTER TABLE Partition Operations” . 

User-defined partitioning and the NDB storage engine (NDB Cluster).  Partitioning by KEY  (including LINEAR KEY ) is the only type of partitioning supported for the NDB  storage engine. It is not possible under normal circumstances in NDB Cluster to create an NDB Cluster table using any partitioning type other than [ LINEAR ] KEY , and attempting to do so fails with an error. 

Exception (not for production) : It is possible to override this restriction by setting the new  system variable on NDB Cluster SQL nodes to ON . If you choose to do this, you should be aware that tables using partitioning types other than [LINEAR] KEY  are not supported in production. In such cases, you can create and use tables with partitioning types other than KEY  or LINEAR KEY , but you do this entirely at your own risk . 

The maximum number of partitions that can be defined for an NDB  table depends on the number of data nodes and node groups in the cluster, the version of the NDB Cluster software in use, and other factors. See NDB and user-defined partitioning, for more information. 

The maximum amount of fixed-size data that can be stored per partition in an NDB  table is 128 TB. Previously, this was 16 GB. 

CREATE TABLE  and ALTER TABLE  statements that would cause a user-partitioned NDB  table not to meet either or both of the following two requirements are not permitted, and fail with an error: 

1. The table must have an explicit primary key. 

2. All columns listed in the table’s partitioning expression must be part of the primary key. 

