Skip navigation links
MySQL 5.1 Reference Manual :: 17 MySQL Cluster NDB 6.X/7.X :: 17.7 Changes in MySQL Cluster NDB 6.X and 7.X :: 17.7.1 Changes in MySQL Cluster NDB 7.1 :: 17.7.1.5 Changes in MySQL Cluster NDB 7.1.0 (5.1.39-ndb-7.1.0) (Not released alpha)
17.7.2 Changes in MySQL Cluster NDB 7.0 »
Section Navigation      [Toggle]

17.7.1.5. Changes in MySQL Cluster NDB 7.1.0 (5.1.39-ndb-7.1.0) (Not released alpha)

This version was for testing and internal use only, and not officially released.

Functionality added or changed:

  • Important Change: The default value of the DiskIOThreadPool data node configuration parameter has changed from 8 to 2.

  • The NDBCLUSTER storage engine now provides native support for default values of table columns. This means that it no longer has to fetch the default values from the MySQL server when performing inserts, making these operations faster and more efficient.

    Important

    Native default value support is enabled for NDBCLUSTER tables created in MySQL Cluster NDB 7.1.0 and later. A table created in a previous version of MySQL Cluster does not automatically support native default values after the cluster is upgraded, but instead continues to use default values supplied by the MySQL server until it is upgraded using an offline ALTER TABLE statement.

    As part of this change, new methods relating to default values have been added to the Column and Table classes in the NDB API. For more information, see Column::getDefaultValue(), Column::setDefaultValue(), and Table::hasDefaultValues().

Bugs fixed:

  • Important Change: The --with-ndb-port-base option for configure has been removed. It is now handled as an unknown and invalid option if you attempt to use it when configuring a build of MySQL Cluster. (Bug#47941)

    See also Bug#38502.

  • The value set by the --ndb-cluster-connection-pool option was not shown in the output of SHOW STATUS LIKE 'NDB%'. (Bug#44118)

  • When building storage engines on Windows it was not possible to specify additional libraries within the CMake file required for the build. An ${engine}_LIBS macro has been added to the files to support these additional storage-engine specific libraries. (Bug#47797)

  • When building a pluggable storage engine on Windows, the engine name could be based on the directory name where the engine was located, rather than the configured storage engine name. (Bug#47795)

  • Installation of MySQL on Windows would fail to set the correct location for the character set files, which could lead to mysqld and mysql failing to initialize properly. (Bug#17270)