Skip navigation links

Additional languages
17.1.5 Known Limitations of MySQL Cluster »
Section Navigation      [Toggle]

17.1.4.6. Features Planned for MySQL Cluster NDB 7.1 and Later

The following improvements to MySQL Cluster are planned for MySQL Cluster NDB 7.1 and later release series.

Important

These features are in planning or early development phase. Timing, availability, and implementation details are not guaranteed, and are subject to change at any time without notice.

  • Native support for default column values.  Starting with MySQL Cluster NDB 7.1.0, default values for table columns are stored in the NDB kernel rather than by the MySQL server as was done previously. This means that inserts on tables having column value defaults can be smaller and faster than before, because less data must be sent from SQL nodes to NDBCLUSTER.

    Tables created using previous MySQL Cluster releases can still be used in MySQL Cluster 7.1.0 and later; however, they do not support native default values until they are upgraded. You can upgrade a table with non-native default values to support native default values using an offline ALTER TABLE statement.

    Further enhancements based on this work that we hope to implement in future MySQL Cluster releases include the following:

    • Decrease NDB space requirements, since there is no longer any need to store the default value for every row

    • Implement REPLACE more efficiently, because there is no need any longer to read the current row before replacing it

    • Provide idempotency in replication for tables having non-nullable columns

  • NDB$INFO meta-information database.  This feature is intended to make it possible to obtain real-time characteristics of a MySQL Cluster by issuing queries from the mysql client or other MySQL client applications. NDB$INFO is a database which is planned for MySQL Cluster NDB 7.1 to provide metadata specific to MySQL Cluster similar to that provided by the INFORMATION_SCHEMA database for the standard MySQL Server. This should eliminate much of the need to read log files, issue DUMP commands, or parse the output of ndb_config in order to get configuration and status information from a running MySQL Cluster.