Known Limitations of NDB Cluster •NDB Cluster •Cluster Direct API (NDBAPI) •Cluster Disk Data •Cluster Replication •ClusterJ This information is intended to be complete with respect to the conditions just set forth. You can report any discrepancies that you encounter to the MySQL bugs database using the instructions given in Section 1.6, “How to Report Bugs or Problems” . Any problem which we do not plan to fix in NDB Cluster 8.0, is added to the list. See Section 23.1.7.11, “Previous NDB Cluster Issues Resolved in NDB Cluster 8.0”  for a list of issues in earlier releases that have been resolved in NDB Cluster 8.0. Limitations and other issues specific to NDB Cluster Replication are described in Section 23.6.3, “Known Issues in NDB Cluster Replication” . Note 23.1.7.1 Noncompliance with SQL Syntax in NDB Cluster Some SQL statements relating to certain MySQL features produce errors when used with  NDB  tables, as described in the following list: • Prefixes.   There are no prefix indexes; only entire columns can be indexed. (The size of an  NDB column 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 23.1.7.6, “Unsupported or Missing Features in NDB Cluster” , for additional information.) • 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  USING HASH  option. • FULLTEXT indexes.   The  NDB  storage engine does not support  FULLTEXT  indexes, which are possible for  MyISAM  and  InnoDB  tables only. However, you can create indexes on  VARCHAR  columns of  NDB  tables. 3965 • TEXT and BLOB columns.   You cannot create indexes on  NDB  table columns that use any of the TEXT  or  BLOB  data types. • Column width.   Attempting to create an index on an  NDB  table 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 TABLE  statement shows the length of the index as 3072. • Indexes and keys in NDB tables.   Keys and indexes on NDB Cluster tables are subject to the following limitations: • Temporary tables.   Temporary tables are not supported. Trying either to create a temporary table that uses the  NDB  storage engine or to alter an existing temporary table to use  NDB  fails with the error  Table storage engine ’ndbcluster’ does not support the create option ’TEMPORARY’ .