MariaDB MaxScale 2.3.17 Release Notes -- 2020-02-11

MariaDB MaxScale 2.3.17 Release Notes -- 2020-02-11

Release 2.3.17 is a GA release.

This document describes the changes in release 2.3.17, when compared to the previous release in the same series.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-2880 Typo in MariaDBMonitor slave connection printing
  • MXS-2878 Monitor connections do not insist on SSL being used
  • MXS-2871 maxscale RPM post-uninstall script has bugs
  • MXS-2859 Strings with newlines break configuration serialization
  • MXS-2857 ssl_verify_peer_certificate should not be on by default
  • MXS-2854 CDC Connector: Schema events aren't processed correctly
  • MXS-2851 CAST Function displays contents of Masked column
  • MXS-2850 MaxScale masking does not work with UNION ALL
  • MXS-2843 remove password info from maxscale log
  • MXS-2839 Not configuring ssl_ca_cert should use system CA
  • MXS-2828 set GCloud firewall rules to make Maxscale tests working
  • MXS-2810 maxscale process still running after uninstalling maxscale package
  • MXS-2801 session_trace doesn't contain all messages
  • MXS-2784 Default charset is not correct

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.

Packaging

RPM and Debian packages are provided for supported the Linux distributions.

Packages can be downloaded here.

Source Code

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 maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.