cc8fb995cd
The `add user` and `enable account` commands create fully privileged administrative users like they did in 2.1. This makes the addition of read-only users backwards compatible. Updated and expanded the documentation on administrative interface users. Added entries into the release notes as well as the upgrading document about relevant changes between 2.1 and 2.2.
27 lines
1.0 KiB
Markdown
27 lines
1.0 KiB
Markdown
# Upgrading MariaDB MaxScale from 2.1 to 2.2
|
|
|
|
This document describes possible issues upgrading MariaDB MaxScale from version
|
|
2.1 to 2.2.
|
|
|
|
For more information about MariaDB MaxScale 2.2, please refer to the
|
|
[ChangeLog](../Changelog.md).
|
|
|
|
For a complete list of changes in MaxScale 2.2.0, refer to the
|
|
[MaxScale 2.2.0 Release Notes](../Release-Notes/MaxScale-2.2.0-Release-Notes.md).
|
|
|
|
Before starting the upgrade, we recommend you back up your current configuration
|
|
file.
|
|
|
|
### Administrative Users
|
|
|
|
The file format for the administrative users used by MaxScale has been
|
|
changed. Old style files are automatically upgraded and a backup of the old file is
|
|
stored in `/var/lib/maxscale/passwd.backup`.
|
|
|
|
### Regular Expression Parameters
|
|
|
|
Modules may now use a built-in regular expression string parameter type instead
|
|
of a normal string when accepting patterns. The modules that use the new regex
|
|
parameter type are *qlafilter* and *tee*. When inputting pattern, enclose the
|
|
string in slashes, e.g. `match=/^select/` defines the pattern `^select`.
|