37 Changes in MySQL NDB Cluster 7.2.2 (5.5.16-ndb-7.2.2) (2011-12-14, Development Milestone Release)

MySQL NDB Cluster 7.2.2 is a new development preview release of NDB Cluster, incorporating new features in the NDB storage engine for testing and user feedback.

Obtaining MySQL NDB Cluster 7.2. MySQL NDB Cluster 7.2 source code and binaries can be obtained from https://dev.mysql.com/downloads/cluster/.

This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.5 through MySQL 5.5.16 (see Changes in MySQL 5.5.16 (2011-09-15, General Availability)).

Functionality Added or Changed

NDB Cluster APIs: Added support for the Memcache API using ndbmemcache, a loadable storage engine for memcached version 1.6 and later, which can be used to provide a persistent MySQL NDB Cluster data store, accessed using the memcache protocol.
The standard memcached caching engine is now included in the MySQL NDB Cluster distribution. Each memcached server, in addition to providing direct access to data stored in a MySQL NDB Cluster, is able to cache data locally and serve (some) requests from this local cache.
The memcached server can also provide an interface to existing MySQL NDB Cluster tables that is strictly defined, so that an administrator can control exactly which tables and columns are referenced by particular memcache keys and values, and which operations are allowed on these keys and values.
For more information, see ndbmemcache—Memcache API for NDB Cluster.
Added the ndbinfo_select_all utility.

Bugs Fixed

Microsoft Windows: The include/storage directory, where the header files supplied for use in compiling MySQL NDB Cluster applications are normally located, was missing from MySQL NDB Cluster release packages for Windows. (Bug #12690665)
NDB Replication: The mysqlbinlog --database option generated table mapping errors when used with NDB tables, unless the binary log was generated using --log-bin-use-v1-row-events=0. (Bug #13067813)
When adding data nodes online, if the SQL nodes were not restarted before starting the new data nodes, the next query to be executed crashed the SQL node on which it was run. (Bug #13715216, Bug #62847)
References: This issue is a regression of: Bug #13117187.