MySQL Cluster 7.3.18 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.3.18, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.3/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! Changes in MySQL NDB Cluster 7.3.18 (5.6.37-ndb-7.3.18) (2017-07-18, General Availability) MySQL NDB Cluster 7.3.18 is a new release of NDB Cluster, based on MySQL Server 5.6 and including features from version 7.3 of the NDB storage engine, as well as fixing a number of recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.3. MySQL NDB Cluster 7.3 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL NDB Cluster 7.3, see What is New in NDB Cluster 7.3 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-3.html). This release also incorporates all bugfixes and changes made in previous NDB Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.37 (see Changes in MySQL 5.6.37 (2017-07-17, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-37.html)). Functionality Added or Changed * Important Change; MySQL NDB ClusterJ: The ClusterJPA plugin for OpenJPA is no longer supported by NDB Cluster, and has been removed from the distribution. (Bug #23563810) Bugs Fixed * NDB Replication: Added a check to stop an NDB replication slave when configuration as a multi-threaded slave is detected (for example, if slave_parallel_workers is set to a nonzero value). (Bug #21074209) * Backup .log files contained log entries for one or more extra fragments, due to an issue with filtering out changes logged by other nodes in the same node group. This resulted in a larger .log file and thus use of more resources than necessary; it could also cause problems when restoring, since backups from different nodes could interfere with one another while the log was being applied. (Bug #25891014) * Error 240 is raised when there is a mismatch between foreign key trigger columns and the values supplied to them during trigger execution, but had no error message indicating the source of the problem. (Bug #23141739) References: See also: Bug #23068914, Bug #85857. * ALTER TABLE .. MAX_ROWS=0 can now be performed only by using a copying ALTER TABLE statement. Resetting MAX_ROWS to 0 can no longer be performed using ALGORITHM=INPLACE or the ONLINE keyword. (Bug #21960004) * When compiling the NDB kernel with gcc version 6.0.0 or later, it is now built using -flifetime-dse=1. (Bug #85381, Bug #25690926) On Behalf of the MySQL/Oracle Release Engineering Team, Kent Boortz & Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster 7.4.16 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.4 makes significant advances in performance; operational efficiency (such as enhanced reporting and faster restarts and upgrades) and conflict detection and resolution for active-active replication between MySQL Clusters. MySQL Cluster 7.4.16 has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.4/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! == Changes in MySQL NDB Cluster 7.4.16 (5.6.37-ndb-7.4.16) (2017-07-18) MySQL NDB Cluster 7.4.16 is a new release of MySQL NDB Cluster 7.4, based on MySQL Server 5.6 and including features in version 7.4 of the NDB storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.4. MySQL NDB Cluster 7.4 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL NDB Cluster 7.4, see What is New in NDB Cluster 7.4 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-4.html). This release also incorporates all bugfixes and changes made in previous NDB Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.37 (see Changes in MySQL 5.6.37 (Not yet released, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-37.html)). * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * NDB Replication: Added the --ndb-log-update-minimal option for logging by mysqld. This option causes only primary key values to be written in the before image, and only changed columns in the after image. (Bug #24438868) * Added the --diff-default option for ndb_config. This option causes the program to print only those parameters having values that differ from their defaults. (Bug #85831, Bug #25844166) * Added the --query-all option to ndb_config. This option acts much like the --query option except that --query-all (short form: -a) dumps configuration information for all attributes at one time. (Bug #60095, Bug #11766869) Bugs Fixed * NDB Replication: Added a check to stop an NDB replication slave when configuration as a multi-threaded slave is detected (for example, if slave_parallel_workers is set to a nonzero value). (Bug #21074209) * NDB Cluster APIs: The implementation method NdbDictionary::NdbTableImpl::getColumn(), used from many places in the NDB API where a column is referenced by name, has been made more efficient. This method used a linear search of an array of columns to find the correct column object, which could be inefficient for tables with many columns, and was detected as a significant use of CPU in customer applications. (Ideally, users should perform name-to-column object mapping, and then use column IDs or objects in method calls, but in practice this is not always done.) A less costly hash index implementation, used previously for the name lookup, is reinstated for tables having relatively many columns. (A linear search continues to be used for tables having fewer columns, where the difference in performance is neglible.) (Bug #24829435) * MySQL NDB ClusterJ: The JTie and NDB JTie tests were skipped when the unit tests for ClusterJ were being run. (Bug #26088583) * Backup .log files contained log entries for one or more extra fragments, due to an issue with filtering out changes logged by other nodes in the same node group. This resulted in a larger .log file and thus use of more resources than necessary; it could also cause problems when restoring, since backups from different nodes could interfere with one another while the log was being applied. (Bug #25891014) * When making the
MySQL Community Server 8.0.2-dmr has been released (part 2/2)
[ This is part 2 of the announcement ] Logging Notes * These error-logging changes have been made: + The server is now more forgiving if it cannot find the configured error-message file (specified using the lc_messages_dir and lc_messages system variable). Previously, the server aborted the startup process and exited. Now the server writes a message to the error log and defaults to built-in English messages. This applies to messages the server writes to the error log and sends to clients. + Error logging is being rewritten to use the MySQL component architecture. Traditional error logging now is implemented using built-in components, and logging using the system log is a loadable component. In addition, a new JSON log writer is available. The log components to use are controlled by the new log_error_services system variable. For more information, see The Error Log (http://dev.mysql.com/doc/refman/8.0/en/error-log.html). Bugs Fixed * Incompatible Change: Plugins such as Group Replication and X Plugin now use the mysql.session account added in this version. If you are upgrading from a previous version which did not include the mysql.session account you must run mysql_upgrade to ensure the account is created. If mysql_upgrade is not run, plugins fail to start with the error message There was an error when trying to access the server with user: mysql.session@localhost. Make sure the user is present in the server and that mysql_upgrade was ran after a server update. (Bug #26042764) References: See also: Bug #24311527, Bug #25642343. * InnoDB: Queries run on INFORMATION_SCHEMA.TABLES performed more slowly with information_schema_stats set to latest. (Bug #26197113) * InnoDB: An ALTER TABLE ... ADD PARTITION operation that specified a DATA DIRECTORY clause failed to ignore the TABLESPACE attribute of the table. (Bug #26113652) * InnoDB: When foreign_key_checks is disabled, a child table with a foreign key constraint can be created before the parent table, which can result in a foreign key constraint failure, as the parent table is unaware of the constraint. When a table is created, there is now a call to load foreign key constraints for the table and check for child tables. (Bug #25976199) * InnoDB: A parsing error occurred while optimizing a table with a full-text index. (Bug #25914332) * InnoDB: Compiling MySQL on Windows with Microsoft Visual C++ 2015 or macOS 10.12.4 with GCC 4.2.1 or Apple LLVM version 8.0.0 (clang-800.0.38) returned warnings. (Bug #25910531) * InnoDB: In debug builds, an assertion was raised during bootstrap when the system tablespace file (ibdata1) ran out of space during creation of doublewrite pages. (Bug #25872368) * InnoDB: Incorrect locking order caused a deadlock when InnoDB attempted to persist an auto-increment counter value to disk. (Bug #25833228) * InnoDB: Internal methods for accessing dictionary table object data did not account for virtual columns. (Bug #25822154) References: This issue is a regression of: Bug #23748128. * InnoDB: The length of a virtual column field in a virtual index record was less than the expected template column length. (Bug #25793677) * InnoDB: In debug builds, shutting down the server with --innodb-fast-shutdown=0 raised an assertion. (Bug #25756224) * InnoDB: The ibd2sdi utility exited when run on an unsupported file type. (Bug #25738491) * InnoDB: InnoDB did not set the compression algorithm when opening a partitioned table. (Bug #25685868) * InnoDB: An in-place ALTER TABLE operation failed to set the encryption type, causing a FLUSH TABLES ... FOR EXPORT operation to assert. (Bug #25672779) * InnoDB: A latch that was held while registering a file close caused a hang condition. (Bug #25658467) * InnoDB: During recovery, prepared transactions were rolled back if the innodb_force_recovery setting was greater than 0. (Bug #25651042) * InnoDB: A CREATE TABLE operation that defined a unique key with an eight character prefix on a NOT NULL TEXT field would raise an assertion if a primary key was not defined. (Bug #25647413) * InnoDB: Updates to data dictionary tables combined with updates to InnoDB system tables for full-text search auxiliary tables raised a lock-related assertion. (Bug #25610353) * InnoDB: The server allocated memory unnecessarily for an operation that rebuilt
MySQL Community Server 8.0.2-dmr has been released (part 1/2)
Dear MySQL users, [Due to file size limitations, the announcement is split in 2 parts. This is part 1.] MySQL Server 8.0.2-dmr (Milestone Release) is a new version of the world's most popular open source database. This is the first public milestone release of MySQL 8.0. http://dev.mysql.com/doc/mysql-development-cycle/en/development-milestone-releases.html As with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data. For information on installing MySQL 8.0.2-dmr on new servers, please see the MySQL installation documentation at http://dev.mysql.com/doc/refman/8.0/en/installing.html MySQL Server 8.0.2-dmr is available in source and binary form for a number of platforms from the "Development Releases" selection of our download pages at http://dev.mysql.com/downloads/mysql/ MySQL Server 8.0.2-dmr is also available from our repository for Linux platforms, go here for details: http://dev.mysql.com/downloads/repo/ Windows packages are available via the Installer for Windows: http://dev.mysql.com/downloads/installer/ along with .ZIP (no-install) packages for more advanced needs. 8.0.2-dmr also comes with a web installer as an alternative to the full installer. The web installer doesn't come bundled with any actual products and instead relies on download-on-demand to fetch only the products you choose to install. This makes the initial download much smaller but increases install time as the individual products will need to be downloaded. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc.: http://bugs.mysql.com/report.php The following link lists the changes in the MySQL 8.0.2-dmr since the release of MySQL 8.0.1. https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-2.html Enjoy! Changes in MySQL 8.0.2 (2017-07-17, Development Milestone) Note This is a milestone release, for use at your own risk. Significant development changes take place in milestone releases and you may encounter compatibility issues, such as data format changes that require attention in addition to the usual procedure of running mysql_upgrade. For example, you may find it necessary to dump your data with mysqldump before the upgrade and reload it afterward. Account Management Notes * During data directory initialization or upgrade, MySQL now creates a 'mysql.session'@'localhost' reserved account. This account is used internally by plugins to access the server. It is locked so that it cannot be used for client conections. (Bug #25642343) * These system variables now are available to permit automatic assignment of roles and to permit granted roles to be automatically activated at client connection time: + mandatory_roles takes a value listing roles that the server should treat as automatically granted to all users. + activate_all_roles_on_login, if enabled, causes all roles granted to users to be made active at client connection time. Character Set Support * For Unicode data that uses NO PAD collations, sorting of multibyte and variable-length values has been improved: + NO PAD collations are those based on UCA 9.0.0 and higher, such as utf8mb4_0900_ai_ci or utf8mb4_ja_0900_as_cs. + The performance improvement is greatest for sparse key values; that is, strings that do not fill their entire permitted length. For a VARCHAR(10) column that uses the utf8mb4_0900_ai_ci collation, values may take up to 40 bytes. The string 'a' is more sparse than 'abcdefghij'. But even 'abcdefghij' uses only 10 bytes of a possible 40 and is more sparse than a string of 10 emojis. The emoji string is dense because each character uses 4 bytes for a resulting string that requires the entire 40 bytes available. (Bug #25750527, Bug #85546) * MySQL now supports a new collation, utf8mb4_0900_as_ci, for the utf8mb4 Unicode character set. This collation is accent sensitive and case insensitive. It is similar to the default utf8mb4 collation (utf8mb4_0900_ai_ci) except that the default collation is accent insensitive. MySQL also now supports a new Japanese collation, utf8mb4_ja_0900_as_cs_ks, for the utf8mb4 Unicode character set. This collation is like utf8mb4_ja_0900_as_cs in that it is accent sensitive and case sensitive, but utf8mb4_ja_0900_as_cs_ks is also kana sensitive and distinguishes Katakana characters from Hiragana characters. utf8mb4_ja_0900_as_cs treats Katakana and Hiragana characters as equal for sorting. Applications that require a Japanese collation but not kana sensitivity
