Some SQL statements relating to certain MySQL features produce
errors when used with
as described in the following list:
Temporary tables. Temporary tables are not supported. Trying either to create a temporary table that uses the
NDBstorage engine or to alter an existing temporary table to use
NDBfails with the error Table storage engine 'ndbcluster' does not support the create option 'TEMPORARY'.
Indexes and keys in NDB tables. Keys and indexes on MySQL Cluster tables are subject to the following limitations:
Column width. Attempting to create an index on an
NDBtable column whose width is greater than 3072 bytes succeeds, but only the first 3072 bytes are actually used for the index. In such cases, a warning Specified key was too long; max key length is 3072 bytes is issued, and a
SHOW CREATE TABLEstatement shows the length of the index as 3072.
FULLTEXT indexes. The
NDBstorage engine does not support
FULLTEXTindexes, which are possible for
USING HASH keys and NULL. Using nullable columns in unique keys and primary keys means that queries using these columns are handled as full table scans. To work around this issue, make the column
NOT NULL, or re-create the index without the
Prefixes. There are no prefix indexes; only entire columns can be indexed. (The size of an
NDBcolumn index is always the same as the width of the column in bytes, up to and including 3072 bytes, as described earlier in this section. Also see Section 3.6.6, “Unsupported or Missing Features in MySQL Cluster”, for additional information.)
BIT columns. A
BITcolumn cannot be a primary key, unique key, or index, nor can it be part of a composite primary key, unique key, or index.
AUTO_INCREMENT columns. Like other MySQL storage engines, the
NDBstorage engine can handle a maximum of one
AUTO_INCREMENTcolumn per table. However, in the case of a Cluster table with no explicit primary key, an
AUTO_INCREMENTcolumn is automatically defined and used as a “hidden” primary key. For this reason, you cannot define a table that has an explicit
AUTO_INCREMENTcolumn unless that column is also declared using the
PRIMARY KEYoption. Attempting to create a table with an
AUTO_INCREMENTcolumn that is not the table's primary key, and using the
NDBstorage engine, fails with an error.
MySQL Cluster and geometry data types. Geometry data types (
WKB) are supported in
NDBtables in MySQL 5.1 (including MySQL Cluster NDB 6.X and 7.X through 7.1). However, spatial indexes are not supported.
Character sets and binary log files. Currently, the
ndb_binlog_indextables are created using the
latin1(ASCII) character set. Because names of binary logs are recorded in this table, binary log files named using non-Latin characters are not referenced correctly in these tables. This is a known issue, which we are working to fix. (Bug #50226)
Creating NDB tables with user-defined partitioning. Support for user-defined partitioning for MySQL Cluster is restricted to [
KEYpartitioning. Beginning with MySQL 5.1.12, using any other partitioning type with
CREATE TABLEstatement results in an error.
It is possible to override this restriction, but doing so is not supported for use in production settings. For details, see User-defined partitioning and the NDB storage engine (MySQL Cluster).
Default partitioning scheme. As of MySQL 5.1.6, all MySQL Cluster tables are by default partitioned by
KEYusing the table's primary key as the partitioning key. If no primary key is explicitly set for the table, the “hidden” primary key automatically created by the
NDBCLUSTERstorage engine is used instead. For additional discussion of these and related issues, see KEY Partitioning.
Beginning with MySQL Cluster NDB 6.2.18, MySQL Cluster NDB 6.3.25, and MySQL Cluster NDB 7.0.6,
ALTER TABLEstatements that would cause a user-partitioned
NDBCLUSTERtable not to meet either or both of the following two requirements are not permitted, and fail with an error (Bug #40709):
The table must have an explicit primary key.
All columns listed in the table's partitioning expression must be part of the primary key.
Exception. If a user-partitioned
NDBCLUSTERtable is created using an empty column-list (that is, using
PARTITION BY [LINEAR] KEY()), then no explicit primary key is required.
Maximum number of partitions for NDBCLUSTER tables. The maximum number of partitions that can defined for a
NDBCLUSTERtable when employing user-defined partitioning is 8 per node group. (See Section 3.2, “MySQL Cluster Nodes, Node Groups, Replicas, and Partitions”, for more information about MySQL Cluster node groups.
DROP PARTITION not supported. It is not possible to drop partitions from
ALTER TABLE ... DROP PARTITION. The other partitioning extensions to
REORGANIZE PARTITION, and
COALESCE PARTITION—are supported for Cluster tables, but use copying and so are not optimized. See Management of RANGE and LIST Partitions and ALTER TABLE Syntax.