MariaDB MaxScale 2.1.2 Release Notes -- 2017-04-03
Release 2.1.2 is a Beta release.
This document describes the changes in release 2.1.2, when compared to release 2.1.1.
For any problems you encounter, please consider submitting a bug report at Jira.
Formatting of IP Addresses and Ports
In practice this means that the address is enclosed by brackets. The port is separated from the address by a colon. Here is an example of the new format:
[192.168.0.201]:3306 [fe80::fa16:54ff:fe8f:7e56]:3306 [localhost]:3306
The first is an IPv4 address, the second an IPv6 address and the last one is a hostname. All of the addresses use port 3306.
- The storage
storage_inmemoryis now the default, so the parameter
storageno longer need to be set explicitly.
Improved Wildcard Matching
The MySQLAuth module now supports all types of wildcards for both IP addresses as well as hostnames.
Configurable Connector-C Plugin Directory
The Connector-C used by MaxScale can now be configured to load authentication
plugins from a specific directory with the new
parameter. Read the Configuration Guide
for more details about this new parameter.
MaxScale now supports IPv6 connections on both the client and backend side as well as being able to listen on IPv6 addresses.
- MXS-1032 missing mysql_clear_password.so plugin
Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.
RPM and Debian packages are provided for the Linux distributions supported by MariaDB Enterprise.
Packages can be downloaded here.
The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is X.Y.Z. Further, master always refers to the latest released non-beta version.
The source code is available here.