hcq/MaxScale
hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove 2.3 release notes from 2.4

Browse Source
This commit is contained in:
Johan Wikman 2019-11-05 11:30:09 +02:00
parent d4a4518155
commit 78521d6452
5 changed files with 0 additions and 223 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
Documentation/Release-Notes/MaxScale-2.3.10-Release-Notes.md
View File

@ -1,49 +0,0 @@
# MariaDB MaxScale 2.3.10 Release Notes -- 2019-08-01
Release 2.3.10 is a GA release.
This document describes the changes in release 2.3.10, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## Bug fixes
* [MXS-2613](https://jira.mariadb.org/browse/MXS-2613) Fix cachefilter diagnostics
* [MXS-2607](https://jira.mariadb.org/browse/MXS-2607) Unexpected trailing spaces with --tsv option in MaxCtrl
* [MXS-2606](https://jira.mariadb.org/browse/MXS-2606) Users are loaded from the first available server
* [MXS-2605](https://jira.mariadb.org/browse/MXS-2605) debug assert at readwritesplit.cc:418 failed: a.second.total == a.second.read + a.second.write
* [MXS-2598](https://jira.mariadb.org/browse/MXS-2598) memory leak on handling COM_CHANGE_USER
* [MXS-2597](https://jira.mariadb.org/browse/MXS-2597) MaxScale doesn't handle errors from microhttpd
* [MXS-2594](https://jira.mariadb.org/browse/MXS-2594) Enabling use_priority for not set priority on server level triggers an election
* [MXS-2587](https://jira.mariadb.org/browse/MXS-2587) mxs1507_trx_replay: debug assert in routeQuery
* [MXS-2586](https://jira.mariadb.org/browse/MXS-2586) user_refresh_time default value is wrong
* [MXS-2559](https://jira.mariadb.org/browse/MXS-2559) Log doesn't tell from which server users are loaded from
* [MXS-2520](https://jira.mariadb.org/browse/MXS-2520) Readwritesplit won't connect to master for reads
* [MXS-2502](https://jira.mariadb.org/browse/MXS-2502) Specifying 'information_schema' as default schema upon connection gives 'access denied'
* [MXS-2490](https://jira.mariadb.org/browse/MXS-2490) Unknown prepared statement handler (0) given to mysqld_stmt_execute
* [MXS-2486](https://jira.mariadb.org/browse/MXS-2486) MaxScale 2.3.6 received fatal signal 11
* [MXS-2449](https://jira.mariadb.org/browse/MXS-2449) Maxadmin shows wrong monitor status
* [MXS-2261](https://jira.mariadb.org/browse/MXS-2261) maxkeys overwrites existing key without warning
* [MXS-1901](https://jira.mariadb.org/browse/MXS-1901) Multi continues COM_STMT_SEND_LONG_DATA route to different backends
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/#mariadb_platform-mariadb_maxscale).
## 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](https://github.com/mariadb-corporation/MaxScale).

33
Documentation/Release-Notes/MaxScale-2.3.11-Release-Notes.md
View File

@ -1,33 +0,0 @@
# MariaDB MaxScale 2.3.11 Release Notes -- 2019-08-02
Release 2.3.11 is a GA release.
This document describes the changes in release 2.3.11, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## Bug fixes
* [MXS-2621](https://jira.mariadb.org/browse/MXS-2621) Incorrect SQL if lower_case_table_names is used.
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/#mariadb_platform-mariadb_maxscale).
## 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](https://github.com/mariadb-corporation/MaxScale).

41
Documentation/Release-Notes/MaxScale-2.3.12-Release-Notes.md
View File

@ -1,41 +0,0 @@
# MariaDB MaxScale 2.3.12 Release Notes -- 2019-09-19
Release 2.3.12 is a GA release.
This document describes the changes in release 2.3.12, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## Bug fixes
* [MXS-2684](https://jira.mariadb.org/browse/MXS-2684) Backend DCB taken from persistent pool is not subject to throttling
* [MXS-2674](https://jira.mariadb.org/browse/MXS-2674) QC bugs
* [MXS-2652](https://jira.mariadb.org/browse/MXS-2652) Maintenance mode lost if node is shutdown
* [MXS-2642](https://jira.mariadb.org/browse/MXS-2642) PAMAuth does not eliminate duplicate PAM services during authentication
* [MXS-2633](https://jira.mariadb.org/browse/MXS-2633) Pam authentication doesn't work with server 10.4
* [MXS-2631](https://jira.mariadb.org/browse/MXS-2631) Duplicate tables found, but it's system tables (information_schema.*, mysql.*)
* [MXS-2609](https://jira.mariadb.org/browse/MXS-2609) Maxscale crash in RWSplitSession::retry_master_query()
* [MXS-2576](https://jira.mariadb.org/browse/MXS-2576) Columnstore Monitor inaccurately labels a UM as slave
* [MXS-2198](https://jira.mariadb.org/browse/MXS-2198) Lacking tarball installation steps in documents
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/#mariadb_platform-mariadb_maxscale).
## 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](https://github.com/mariadb-corporation/MaxScale).

47
Documentation/Release-Notes/MaxScale-2.3.13-Release-Notes.md
View File

@ -1,47 +0,0 @@
# MariaDB MaxScale 2.3.13 Release Notes -- 2019-10-30
Release 2.3.13 is a GA release.
This document describes the changes in release 2.3.13, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## Bug fixes
* [MXS-2733](https://jira.mariadb.org/browse/MXS-2733) UTC_TIMESTAMP not recognized as a built-in function
* [MXS-2721](https://jira.mariadb.org/browse/MXS-2721) MaxScale 2.4.2 crashes on different lxc containers with similar error
* [MXS-2720](https://jira.mariadb.org/browse/MXS-2720) maxctrl and maxadmin report negative number of connections to a service
* [MXS-2713](https://jira.mariadb.org/browse/MXS-2713) SET PASSWORD statement sent to all nodes, not only to master
* [MXS-2712](https://jira.mariadb.org/browse/MXS-2712) maxctrl help does not explain meaning of the output columns of some commands
* [MXS-2706](https://jira.mariadb.org/browse/MXS-2706) Maxscale maxinfo plugin breaks maxscale_exporter (JSON output all strings)
* [MXS-2699](https://jira.mariadb.org/browse/MXS-2699) Two QC bugs
* [MXS-2694](https://jira.mariadb.org/browse/MXS-2694) COM_BINLOG_DUMP confuses readwritesplit
* [MXS-2688](https://jira.mariadb.org/browse/MXS-2688) SET should be classified as QUERY_TYPE_SESSION_WRITE
* [MXS-2673](https://jira.mariadb.org/browse/MXS-2673) Sys var and user var combined issue
* [MXS-2645](https://jira.mariadb.org/browse/MXS-2645) Session client count is not always decremented when closing session
* [MXS-2639](https://jira.mariadb.org/browse/MXS-2639) maxinfo memory leak
* [MXS-2620](https://jira.mariadb.org/browse/MXS-2620) Document that shutting down the master can break auto_rejoin and lose transactions
* [MXS-2610](https://jira.mariadb.org/browse/MXS-2610) [AVRO ROUTER] Maxscale Crash
* [MXS-2600](https://jira.mariadb.org/browse/MXS-2600) Documentation is inconsistent regarding privileges for MariaDB Monitor
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/#mariadb_platform-mariadb_maxscale).
## 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](https://github.com/mariadb-corporation/MaxScale).

53
Documentation/Release-Notes/MaxScale-2.3.9-Release-Notes.md
View File

@ -1,53 +0,0 @@
# MariaDB MaxScale 2.3.9 Release Notes -- 2019-07-04
Release 2.3.9 is a GA release.
This document describes the changes in release 2.3.9, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## New Features
* [MXS-2480](https://jira.mariadb.org/browse/MXS-2480) Write paths to opened sqlite3 databases in log when log_info is set
## Bug fixes
* [MXS-2582](https://jira.mariadb.org/browse/MXS-2582) Intermittent unknown statement handler errors from backends
* [MXS-2578](https://jira.mariadb.org/browse/MXS-2578) Maxscale RPM issue PCI Compliancy
* [MXS-2575](https://jira.mariadb.org/browse/MXS-2575) PATCH with invalid credentials returns no result
* [MXS-2574](https://jira.mariadb.org/browse/MXS-2574) maxctrl alter user doesn't work on current user
* [MXS-2569](https://jira.mariadb.org/browse/MXS-2569) No newline sent with large schemas
* [MXS-2563](https://jira.mariadb.org/browse/MXS-2563) Failing debug assertion at rwsplitsession.cc:1129 : m_expected_responses == 0
* [MXS-2562](https://jira.mariadb.org/browse/MXS-2562) Oracle's MySQL Connector/ODBC gets packets out-of-order errors with .NET
* [MXS-2560](https://jira.mariadb.org/browse/MXS-2560) KILL with recursive services doesn't work
* [MXS-2551](https://jira.mariadb.org/browse/MXS-2551) Monitors add deprecated parameters to persisted config files
* [MXS-2550](https://jira.mariadb.org/browse/MXS-2550) qlafilter escapes newline with two quotes and a space
* [MXS-2549](https://jira.mariadb.org/browse/MXS-2549) prelink can corrupt maxctrl
* [MXS-2547](https://jira.mariadb.org/browse/MXS-2547) Stop MaxScale during Rest-API query cause process hung
* [MXS-2521](https://jira.mariadb.org/browse/MXS-2521) COM_STMT_EXECUTE maybe return empty result
* [MXS-2490](https://jira.mariadb.org/browse/MXS-2490) Unknown prepared statement handler (0) given to mysqld_stmt_execute
* [MXS-2461](https://jira.mariadb.org/browse/MXS-2461) Unexpected internal state with ReadWriteSplit and proxy_protocol=true
* [MXS-2442](https://jira.mariadb.org/browse/MXS-2442) "Param1 reported as VARIABLE" warnings
* [MXS-2367](https://jira.mariadb.org/browse/MXS-2367) No warning about missing REPLICATION SLAVE
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/mariadb-tx/maxscale).
## 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](https://github.com/mariadb-corporation/MaxScale).