The following limitations apply to the use of storage engines with user-defined partitioning of tables.
MERGE storage engine.
User-defined partitioning and the
storage engine are not compatible. Tables using the
MERGE storage engine cannot be partitioned.
Partitioned tables cannot be merged.
FEDERATED storage engine.
FEDERATED tables is not
supported; it is not possible to create partitioned
FEDERATED tables. We are working to remove
this limitation in a future MySQL release.
CSV storage engine.
Partitioned tables using the
engine are not supported; it is not possible to create
NDBCLUSTER storage engine (MySQL Cluster).
KEY) is the only type of partitioning supported for
NDBCLUSTER storage engine. It
is not possible to create a MySQL Cluster table using any
partitioning type other than [
KEY, and attempting to do so fails with an
In addition, the maximum number of partitions that can be
defined for an
NDBCLUSTER table is
8 times the number of node groups in the cluster. (See
MySQL Cluster Nodes, Node Groups, Replicas, and Partitions, for more
information about node groups in MySQL Cluster.)
Upgrading partitioned tables.
When performing an upgrade, tables which are partitioned by
KEY and which use any storage engine other
NDBCLUSTER must be dumped
Same storage engine for all partitions. All partitions of a partitioned table must use the same storage engine and it must be the same storage engine used by the table as a whole. In addition, if one does not specify an engine on the table level, then one must do either of the following when creating or altering a partitioned table:
Do not specify any engine for any partition or subpartition
Specify the engine for all partitions or subpartitions
We are working to remove this limitation in a future MySQL release.