MySQL Utilities is now its own product, and is no longer a sub-product of MySQL Workbench.
This RC release is not available on Microsoft Windows.
Fabric now supports the MySQL Client-Server Protocol. Only connectors and clients supporting PROTOCOL41 and MULTI_RESULTSET are allowed. This preferred interface is an alternative to the current XML-RPC interface.
The internal interface between the protocol classes and the Fabric core was improved to be more consistent.
Fabric now supports DATETIME and UTF-8 strings as sharding keys in range-based sharding.
Provisioning support was added to Fabric, by supporting the Nova Interface, which is responsible for managing compute instances to easily expand and shrink the number of servers in a group when MySQL Fabric is deployed within an OpenStack Cloud Provider. This introduces commands for the provider, machine, and snapshot groups.
The specification and control files were updated to reflect the Connector/Python 2.0.0+ dependency. (Bug #19380554)
Added support for Connector/Python 2.0.0 and higher. (Bug #19215979)
The mysqlreplicate and
mysqlrplms utilities would generate an
exception when the optional
not passed in.
The check for an errant transaction was not performed for mysqlrpladmin's switchover command, it only performed for the failover command. Both commands now check for errant transactions.
The errant transaction check requires all servers in the topology to have GTID enabled, otherwise a warning is issued indicating that the check cannot be performed for the switchover command. (Bug #19076488, Bug #73110)
When a login-path (or config-path) was used for server
connection values, and the
file was not found, an AttributeError was issued instead of a
missing file error.
On OS X Mavericks, the testing suite (MUT) failed to kill mysqld processes as MUT could not identify the MySQL server ports. (Bug #18958536)
On Windows, the mysqlfabric utility searched for the fabric configuration file outside of the installation folder.
The default configuration file location is
Files (x86)\MySQL\MySQL Utilities
Additionally, the MySQL Utilities section in the Windows Start menu now contains a link to the fabric configuration file. (Bug #18904014)
With fabric, the
--daemonize parameter was
not recognized when passed in with
(Bug #18874603, Bug #72818)
In the mysqluc environment, pressing tab after typing a "q" would incorrectly suggest the term "qxit" instead of "quit". This now returns "quit", which is an alias for "exit". (Bug #18852960, Bug #72776)
On Linux, the backspace key was not functioning in the mysqluc environment, therefore the entered text could not be changed. (Bug #18852933, Bug #72777)
The Debian packages checked for a Connector/Python 1.0.9+ prerequisite instead of requiring Connector/Python 1.2.1+. (Bug #18838462)
Failed MySQL server connection error messages now return the actual error returned from the failed connection, instead of a custom (and more generic) error. This new behavior is more standard with how other MySQL client applications behave. (Bug #18815545, Bug #72670)
--discover-slaves-login option, if
there were connection or configuration problems with some of the
slaves, then those slaves were skipped with only a generic error
message being issued. This behavior did not change when also
A simple warning about the connection/configuration problems is
now generated during the discovery process, and it references
--verbose to see additional
--verbose option generates
specific information for each slave, and includes their
(Bug #18815523, Bug #72706)
When running the mysqlserverinfo utility as
root against an offline MySQL server, it failed to start a
read-only instance of the server and emitted the fatal error
"Please read "Security" section of the manual to find out how to
run mysqld as root!". This occurred because the mysqld option
"--user=root" was not passed in, which is mandatory when
starting mysqld as root. The
user_name that executes the utility
is now detected and added as
when starting the read-only MySQL server.
Additionally, error checks were added that validate the
options to check for their existence and accessibility.
(Bug #18790361, Bug #72658)
Descriptive text for the
was improved to clearly indicate which formats it supports. For
example, it does not support the "vertical" format.
(Bug #18790134, Bug #72659)
The minimum required Connector/Python version in the source code was defined as 1.0.9 instead of 1.2.1. (Bug #18777318, Bug #72664)
When cloning a user, the mysqluserclone utility did not check if the user of the destination server had the required privileges for a successful operation. (Bug #18768780, Bug #72655)
The mysqluserclone utility was throwing an
unhandled exception when the
was used with incorrect login credentials. The error message is
(Bug #18768487, Bug #72656)
The mysqluc utility would suddenly exit when a command was wrongly formatted, like when a closing quote was missing. This action now generates a warning instead of exiting from the console, which allows the command to be edited. (Bug #18730815, Bug #72569)
When passing in the
--dump option to the
mysqluserclone utility on a user with the
hostname '%', the output (each grant) would be printed twice.
(Bug #18730720, Bug #72570)
Error messages for the mysqluserclone utility were improved by making them more explicit in terms of what might be missing. (Bug #18730656, Bug #72572)
sharding prune_shard operations
would hang when performed on a very large number of records.
(Bug #18669231, Bug #19177860, Bug #73238)
The default value was removed from the
--rpl-user option for the
mysqlrplms utilities. Before, the default
user/pass value was "rpl:rpl".
A warning is now emitted whenever a password is entered into the
command line. When testing, this warning can be disabled by
self.mask_global to false.
The mysqlfailover utility caused excessive
CPU load when executed in the console without passing in
--daemon. This high CPU usage was due to the
process waiting for user input.
(Bug #18379971, Bug #72002)