This was intended as a replacement release for MySQL Cluster NDB 7.0.15, fixing a critical issue in that version that was discovered shortly after its release (Bug #54242); however, MySQL Cluster NDB 7.0.15a was not actually released due to Bug #54516 being found during testing. Users of MySQL Cluster NDB 7.0.14 or MySQL Cluster NDB 7.0.15 should upgrade to the 7.0.15b release as soon as possible.
The latest MySQL Cluster NDB 7.0 binaries for supported platforms can be obtained from http://dev.mysql.com/downloads/cluster/. Source code for the latest MySQL Cluster NDB 7.0 release can be obtained from the same location.
This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.1 through MySQL 5.1.44 (see Changes in MySQL 5.1.44 (2010-02-04)).
When using mysqldump to back up and restore schema information while using ndb_restore for restoring only the data, restoring to MySQL Cluster NDB 7.1.4 from an older version failed on tables having columns with default values. This was because versions of MySQL Cluster prior to MySQL Cluster NDB 7.1.4 did not have native support for default values.
In addition, the MySQL Server supports
TIMESTAMPcolumns having dynamic default values, such as
DEFAULT CURRENT_TIMESTAMP; however, the current implementation of
NDB-native default values permits only a constant default value.
To fix this issue, the manner in which
TIMESTAMPcolumns is reverted to its pre-NDB-7.1.4 behavior (obtaining the default value from mysqld rather than
NDBCLUSTER) except where a
TIMESTAMPcolumn uses a constant default, as in the case of a column declared as
TIMESTAMP DEFAULT 0or
TIMESTAMP DEFAULT 20100607174832. (Bug #54242)