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

Update ChangeLog

Browse Source
This commit is contained in:
Johan Wikman
2016-09-26 18:12:36 +03:00
parent 997fe6b90b
commit 8fc6f52eea
1 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
Documentation/Changelog.md
View File

@ -5,14 +5,13 @@
* SSL can be used in the communication between MariaDB MaxScale and the backend servers. * SSL can be used in the communication between MariaDB MaxScale and the backend servers.
* The number of allowed connections can explicitly be throttled. * The number of allowed connections can explicitly be throttled.
* MariaDB MaxScale can continue serving read request even if the master has gone down. * MariaDB MaxScale can continue serving read request even if the master has gone down.
* The security of MaxAdmin has been improved; you can only connect from the * The security of MaxAdmin has been improved; Unix domain sockets can be used in the
same host MariaDB MaxScale is running on, and the Linux identity is used for communication with MariaDB MaxScale and the Linux identity can be used for authorization.
authorization.
* MariaDB MaxScale can in real time make binlog events available as raw AVRO or * MariaDB MaxScale can in real time make binlog events available as raw AVRO or
as JSON objects (beta level functionality). as JSON objects (beta level functionality).
For more details, please refer to: For more details, please refer to:
* [MariaDB MaxScale 2.0.0 Release Notes](Release-Notes/MaxScale-2.0.0-Release-Notes.md) * [MariaDB MaxScale 2.0.1 Release Notes](Release-Notes/MaxScale-2.0.1-Release-Notes.md)
## MariaDB MaxScale 1.4 ## MariaDB MaxScale 1.4
* Authentication now allows table level resolution of grants. MaxScale service * Authentication now allows table level resolution of grants. MaxScale service