From 25350d6a080d30730a4f89c1a92a9e0ffe29e39a Mon Sep 17 00:00:00 2001 From: Johan Wikman Date: Wed, 8 Mar 2017 13:17:17 +0200 Subject: [PATCH] Update change log and release notes --- Documentation/Changelog.md | 5 +++ .../MaxScale-2.1.1-Release-Notes.md | 37 +++++++++++++++++-- 2 files changed, 38 insertions(+), 4 deletions(-) diff --git a/Documentation/Changelog.md b/Documentation/Changelog.md index a063e96fb..eb6d1760f 100644 --- a/Documentation/Changelog.md +++ b/Documentation/Changelog.md @@ -14,8 +14,13 @@ * Named Server Filter now supports wildcards for source option. * Binlog Server can now be configured to encrypt binlog files. * New filters, _cache_, _ccrfilter_, _insertstream_, _masking_, and _maxrows_ are introduced. +* GSSAPI based authentication can be used +* Prepared statements are now in the database firewall filtered exactly like non-prepared + statements. +* The firewall filter can now filter based on function usage. For more details, please refer to: +* [MariaDB MaxScale 2.1.1 Release Notes](Release-Notes/MaxScale-2.1.1-Release-Notes.md) * [MariaDB MaxScale 2.1.0 Release Notes](Release-Notes/MaxScale-2.1.0-Release-Notes.md) ## MariaDB MaxScale 2.0 diff --git a/Documentation/Release-Notes/MaxScale-2.1.1-Release-Notes.md b/Documentation/Release-Notes/MaxScale-2.1.1-Release-Notes.md index 540f0b5a4..39d65b1a6 100644 --- a/Documentation/Release-Notes/MaxScale-2.1.1-Release-Notes.md +++ b/Documentation/Release-Notes/MaxScale-2.1.1-Release-Notes.md @@ -3,7 +3,11 @@ Release 2.1.1 is a Beta release. This document describes the changes in release 2.1.1, when compared to -release 2.1.0. +release [2.1.0](MaxScale-2.1.0-Release-Notes.md). + +If you are upgrading from release 2.0, please also read the following +release notes: +[2.1.0](./MaxScale-2.1.0-Release-Notes.md) For any problems you encounter, please consider submitting a bug report at [Jira](https://jira.mariadb.org). @@ -12,9 +16,20 @@ report at [Jira](https://jira.mariadb.org). ### Cache -The cache will now _also_ be used and populated in a transaction that is +* The cache will now _also_ be used and populated in a transaction that is _not_ explicitly read only, but only until the first statement that modifies the database is encountered. +* SELECT statements that refer to user or system variables are not cached. +* SELECT statements using functions whose result depend upon the current +user or context are not cached. Examples of such functions are `USER()`, +`RAND()` or `CURRENT_TIME()`. + +### Firewall Filter + +* Prepared statements are now treated exactly like non-prepared statements. +* Statements can now be accepted/rejected based upon function usage. + +*NOTE* Both of these features were available already in _2.1.0_. ## Dropped Features @@ -43,14 +58,28 @@ after a failover has been triggered. This makes it possible for external actors to recover the failed nodes without having to manually clear the maintenance mode. -For more information about the failover mode and how it works, read the +For more information about the failover mode and how it works, please read the [MySQL Monitor](../Monitors/MySQL-Monitor.md) documentation. +### GSSAPI + +_GASSAPI_ based authentication can now be used with MaxScale. + +For more information, please read the +[GSSAPI Authentication](../Authenticators/GSSAPI-Authenticator.md) documentation. + +NOTE This feature was available already in _2.1.0_. + ## Bug fixes [Here is a list of bugs fixed since the release of MaxScale 2.1.0.](https://jira.mariadb.org/issues/?jql=project%20%3D%20MXS%20AND%20issuetype%20%3D%20Bug%20AND%20resolution%20in%20(Fixed%2C%20Done)%20AND%20fixVersion%20%3D%202.1.1%20AND%20fixVersion%20NOT%20IN%20(2.1.0)) -* +* [MXS-1165](https://jira.mariadb.org/browse/MXS-1165) MaxInfo eat too much memory when getting list of session and client. +* [MXS-1143](https://jira.mariadb.org/browse/MXS-1143) Add support for new MariaDB 10.2 flags +* [MXS-1130](https://jira.mariadb.org/browse/MXS-1130) Unexpected length encoding 'ff' encountered +* [MXS-1081](https://jira.mariadb.org/browse/MXS-1081) Avro data file corruption +* [MXS-1077](https://jira.mariadb.org/browse/MXS-1077) Resource Leak +* [MXS-759](https://jira.mariadb.org/browse/MXS-759) Starting MaxScale from command line fails on CentOS 7 ## Known Issues and Limitations