Merge branch '2.1' into 2.2
This commit is contained in:
@ -21,6 +21,7 @@
|
||||
* MaxScale now supports IPv6
|
||||
|
||||
For more details, please refer to:
|
||||
* [MariaDB MaxScale 2.1.9 Release Notes](Release-Notes/MaxScale-2.1.9-Release-Notes.md)
|
||||
* [MariaDB MaxScale 2.1.8 Release Notes](Release-Notes/MaxScale-2.1.8-Release-Notes.md)
|
||||
* [MariaDB MaxScale 2.1.7 Release Notes](Release-Notes/MaxScale-2.1.7-Release-Notes.md)
|
||||
* [MariaDB MaxScale 2.1.6 Release Notes](Release-Notes/MaxScale-2.1.6-Release-Notes.md)
|
||||
|
45
Documentation/Release-Notes/MaxScale-2.1.9-Release-Notes.md
Normal file
45
Documentation/Release-Notes/MaxScale-2.1.9-Release-Notes.md
Normal file
@ -0,0 +1,45 @@
|
||||
# MariaDB MaxScale 2.1.9 Release Notes
|
||||
|
||||
Release 2.1.9 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.1.9, when compared to release
|
||||
[2.1.8](MaxScale-2.1.8-Release-Notes.md).
|
||||
|
||||
If you are upgrading from release 2.0, please also read the following release
|
||||
notes:
|
||||
|
||||
* [2.1.8](./MaxScale-2.1.8-Release-Notes.md)
|
||||
* [2.1.7](./MaxScale-2.1.7-Release-Notes.md)
|
||||
* [2.1.6](./MaxScale-2.1.6-Release-Notes.md)
|
||||
* [2.1.5](./MaxScale-2.1.5-Release-Notes.md)
|
||||
* [2.1.4](./MaxScale-2.1.4-Release-Notes.md)
|
||||
* [2.1.3](./MaxScale-2.1.3-Release-Notes.md)
|
||||
* [2.1.2](./MaxScale-2.1.2-Release-Notes.md)
|
||||
* [2.1.1](./MaxScale-2.1.1-Release-Notes.md)
|
||||
* [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).
|
||||
|
||||
## Bug fixes
|
||||
|
||||
[Here is a list of bugs fixed in MaxScale 2.1.9.](https://jira.mariadb.org/issues/?jql=project%20%3D%20MXS%20AND%20issuetype%20%3D%20Bug%20AND%20status%20%3D%20Closed%20AND%20fixVersion%20%3D%202.1.9)
|
||||
|
||||
* [MXS-1435](https://jira.mariadb.org/browse/MXS-1435) Persistent connections can hang on COM_QUIT
|
||||
* [MXS-1377](https://jira.mariadb.org/browse/MXS-1377) maxscale doesn't cleanup pid file on startup error
|
||||
* [MXS-1295](https://jira.mariadb.org/browse/MXS-1295) MaxScale's readwritesplit router does not take into account the fact that stored procedure call may change the value of a user variable
|
||||
|
||||
## Packaging
|
||||
|
||||
RPM and Debian packages are provided for the Linux distributions supported by
|
||||
MariaDB Enterprise.
|
||||
|
||||
Packages can be downloaded [here](https://mariadb.com/resources/downloads).
|
||||
|
||||
## 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.
|
||||
|
||||
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).
|
@ -237,6 +237,15 @@ multi-statement queries.
|
||||
router_options=strict_multi_stmt=false
|
||||
```
|
||||
|
||||
### `strict_sp_calls`
|
||||
|
||||
Similar to `strict_multi_stmt`, this option allows all queries after a CALL
|
||||
operation on a stored procedure to be routed to the master. This option is
|
||||
disabled by default and was added in MaxScale 2.1.9.
|
||||
|
||||
All warnings and restrictions that apply to `strict_multi_stmt` also apply to
|
||||
`strict_sp_calls`.
|
||||
|
||||
### `master_failure_mode`
|
||||
|
||||
This option controls how the failure of a master server is handled. By default,
|
||||
|
@ -7,6 +7,7 @@ For more information about MariaDB MaxScale 2.1, please refer to the
|
||||
[ChangeLog](../Changelog.md).
|
||||
|
||||
For a complete list of changes in MaxScale 2.1, refer to the
|
||||
[MaxScale 2.1.9 Release Notes](../Release-Notes/MaxScale-2.1.9-Release-Notes.md).
|
||||
[MaxScale 2.1.8 Release Notes](../Release-Notes/MaxScale-2.1.8-Release-Notes.md).
|
||||
[MaxScale 2.1.7 Release Notes](../Release-Notes/MaxScale-2.1.7-Release-Notes.md).
|
||||
[MaxScale 2.1.6 Release Notes](../Release-Notes/MaxScale-2.1.6-Release-Notes.md).
|
||||
|
@ -7,5 +7,8 @@ then
|
||||
exit 1
|
||||
fi
|
||||
|
||||
# Script location
|
||||
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
|
||||
|
||||
version=$1
|
||||
curl -s "https://jira.mariadb.org/sr/jira.issueviews:searchrequest-csv-current-fields/temp/SearchRequest.csv?jqlQuery=project+%3D+MXS+AND+issuetype+%3D+Bug+AND+status+%3D+Closed+AND+fixVersion+%3D+$version" | process.pl
|
||||
curl -s "https://jira.mariadb.org/sr/jira.issueviews:searchrequest-csv-current-fields/temp/SearchRequest.csv?jqlQuery=project+%3D+MXS+AND+issuetype+%3D+Bug+AND+status+%3D+Closed+AND+fixVersion+%3D+$version" | $DIR/process.pl
|
||||
|
@ -7,5 +7,8 @@ then
|
||||
exit 1
|
||||
fi
|
||||
|
||||
# Script location
|
||||
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
|
||||
|
||||
version=$1
|
||||
curl -s "https://jira.mariadb.org/sr/jira.issueviews:searchrequest-csv-current-fields/temp/SearchRequest.csv?jqlQuery=project+%3D+MXS+AND+issuetype+%21%3D+Bug+AND+status+%3D+Closed+AND+fixVersion+%3D+$version"|process.pl
|
||||
curl -s "https://jira.mariadb.org/sr/jira.issueviews:searchrequest-csv-current-fields/temp/SearchRequest.csv?jqlQuery=project+%3D+MXS+AND+issuetype+%21%3D+Bug+AND+status+%3D+Closed+AND+fixVersion+%3D+$version" | $DIR/process.pl
|
||||
|
@ -1,4 +1,4 @@
|
||||
#!/bin/perl
|
||||
#!/usr/bin/env perl
|
||||
|
||||
# Discard the CSV headers
|
||||
<>;
|
||||
@ -16,5 +16,5 @@ while (<>)
|
||||
my $issue = @parts[1];
|
||||
my $desc = @parts[0];
|
||||
|
||||
print "* ($issue)[https://jira.mariadb.org/browse/$issue] $desc\n";
|
||||
print "* [$issue](https://jira.mariadb.org/browse/$issue) $desc\n";
|
||||
}
|
||||
|
Reference in New Issue
Block a user