Documentation Home
MySQL Installer Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 175.4Kb
PDF (A4) - 174.9Kb
HTML Download (TGZ) - 47.1Kb
HTML Download (Zip) - 104.4Kb

MySQL Installer Release Notes  /  Changes in MySQL Installer 1.4.29 (2019-03-06)

Changes in MySQL Installer 1.4.29 (2019-03-06)

Known limitation: There is an issue for MySQL 8.0.16 and higher that prevents the server from starting when the data directory from an earlier server version is reused for a new server installation. MySQL Server automatically initiates an upgrade when an existing data directory from an earlier server installation is reused and MySQL Installer does not process the upgrade as expected.

The workaround is to use the Upgrade operation in MySQL Installer, instead of removing the earlier server installation and then installing a fresh server instance that reuses the previous data directory. Alternatively, install a new server instance with the same version number as the data directory to be reused, then upgrade the server afterwards.

Functionality Added or Changed

  • Previously, MySQL Installer ran mysql_upgrade as a secondary step when a server upgrade operation was performed. Now that mysql_upgrade is deprecated, MySQL Installer performs the schema upgrade directly when the server upgrade is executed (see Important server upgrade conditions).

  • MySQL Installer now supports an easy-to-use configuration setup for production InnoDB Clusters on Microsoft Windows, in addition to continued support for sandbox InnoDB Clusters. Separate configuration operations enable the creation or expansion of clusters without the use of complex commands or specialized scripts.

    For the deployment of a production cluster, MySQL Installer must run on each host inside a local network to install and configure the required server instances in the cluster.

Bugs Fixed

  • An error in the product manifest prevented the configuration of MySQL 8.0 and 5.7 server instances from finishing successfully. The server instance was installed properly, but it was not configured. (Bug #29611546)

  • An existing MySQL 5.7 sandbox InnoDB Cluster could not be recreated after an upgrade was performed on the base server instance (used to configure the cluster). (Bug #29410843)

  • A disclaimer was added to the sandbox-configuration process stating that recreating the sandbox cluster will delete the existing data within the cluster. (Bug #29371916)

  • An error was generated during the reconfigure operation when a server instance, configured as a sandbox InnoDB Cluster using the mysql_native_password authentication plugin initially, was reconfigured as a standalone server using the mysql_native_password authentication plugin. (Bug #29299204)