 fa99b97dbd
			
		
	
	fa99b97dbd
	
	
	
		
			
			The release notes now mention that the tee filter has been rewritten and it requires some extra configuration.
		
			
				
	
	
		
			113 lines
		
	
	
		
			4.0 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
			
		
		
	
	
			113 lines
		
	
	
		
			4.0 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
| # MariaDB MaxScale 2.2.0 Release Notes
 | |
| 
 | |
| Release 2.2.0 is a Beta release.
 | |
| 
 | |
| This document describes the changes in release 2.2.0, when compared to
 | |
| release 2.1.X.
 | |
| 
 | |
| For any problems you encounter, please consider submitting a bug
 | |
| report at [Jira](https://jira.mariadb.org).
 | |
| 
 | |
| ## Changed Features
 | |
| 
 | |
| ### Whitespace in Object Names
 | |
| 
 | |
| Significant whitespace in object names is now deprecated. All object names
 | |
| (services, servers, etc.) will be converted to a compatible format by
 | |
| squeezing repeating whitespace and replacing it with hyphens. If any
 | |
| object name conversions take place, a warning will be logged.
 | |
| 
 | |
| ### NamedServerFilter
 | |
| 
 | |
| This filter now uses the PCRE2-libarary to match queries. Previously, it used
 | |
| the POSIX-version of PCRE2. The filter also accepts multiple match-server pairs.
 | |
| Please see the NamedServerFilter documentation for details.
 | |
| 
 | |
| ### Tee Filter
 | |
| 
 | |
| The `tee` filter has been rewritten to better suit the way MaxScale now
 | |
| functions. The filter requires that the service where the branched session is
 | |
| created has at least one network listener. The users must also be able to
 | |
| connect from the local MaxScale host. Usually this means that an extra grant for
 | |
| the loopback address is required (e.g. `myuser@127.0.0.1`).
 | |
| 
 | |
| In addition to the aforementioned requirements, a failure to create a branched
 | |
| session no longer causes the actual client session to be closed. In most cases,
 | |
| this is desired behavior.
 | |
| 
 | |
| ## Dropped Features
 | |
| 
 | |
| ### MaxAdmin
 | |
| 
 | |
| The following deprecated commands have been removed:
 | |
| 
 | |
| * `enable log [debug|trace|message]`
 | |
| * `disable log [debug|trace|message]`
 | |
| * `enable sessionlog [debug|trace|message]`
 | |
| * `disable sessionlog [debug|trace|message]`
 | |
| 
 | |
| The following commands have been deprecated:
 | |
| 
 | |
| * `enable sessionlog-priority <session-id> [debug|info|notice|warning]`
 | |
| * `disable sessionlog-priority <session-id> [debug|info|notice|warning]`
 | |
| 
 | |
| The commands can be issued, but have no effect.
 | |
| 
 | |
| MaxAdmin no longer attempts to interpret additional command line parameters as a
 | |
| file name to load commands from  (e.g. `maxadmin mycommands.txt`). The shell
 | |
| indirection operator `<` should be used to achieve the same effect (`maxadmin <
 | |
| mycommands.txt`).
 | |
| 
 | |
| ## New Features
 | |
| 
 | |
| ### MySQL Monitor Crash Safety
 | |
| 
 | |
| The MySQL monitor keeps a journal of the state of the servers and the currently
 | |
| elected master. This information will be read if MaxScale suffers an
 | |
| uncontrolled shutdown. By doing the journaling of server states, the mysqlmon
 | |
| monitor is able to keep track of stale master and stale slave states across
 | |
| restarts and crashes.
 | |
| 
 | |
| ### Avrorouter `deflate` compression
 | |
| 
 | |
| The Avrorouter now supports the `deflate` compression method. This allows the
 | |
| stored Avro format files to be compressed on disk. For more information, refer
 | |
| to the [Avrorouter](../Routers/Avrorouter.md) documentation.
 | |
| 
 | |
| ### Preliminary proxy protocol support
 | |
| 
 | |
| The MySQL backend protocol module now supports sending a proxy protocol header
 | |
| to the server. For more information, see the server section in the
 | |
| [Configuration guide](../Getting-Started/Configuration-Guide.md).
 | |
| 
 | |
| ### KILL command support
 | |
| 
 | |
| The MySQL client protocol now detects `KILL <thread_id>` statements (binary and
 | |
| query forms) and kills the MaxScale session with the given id. This feature has
 | |
| some limitations, see [Limitations](../About/Limitations.md) for more
 | |
| information.
 | |
| 
 | |
| ## Bug fixes
 | |
| 
 | |
| [Here is a list of bugs fixed since the release of MaxScale 2.1.X.]()
 | |
| 
 | |
| ## 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 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 X.Y.Z. Further, *master* always refers to the latest released non-beta version.
 | |
| 
 | |
| The source code is available [here](https://github.com/mariadb-corporation/MaxScale).
 |