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

Added missing schemarouter parameter documentation

Browse Source 
The `ignore_databases` and `ignore_databases_regex` were missing from
the schemarouter documentation.
This commit is contained in:
Markus Makela
2016-02-12 21:19:38 +02:00
parent 3aca2978d0
commit 062373d8da
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
Routers/SchemaRouter.md
View File

@ -50,6 +50,9 @@ The schemarouter supports the following router options:
|disable_sescmd_history|true, false|Disable the session command history. This will prevent growing memory consumption of a long-running session and allows pooled connections to MaxScale to be used. The drawback of this is the fact that if a server goes down, the session state will not be consistent anymore.| |disable_sescmd_history|true, false|Disable the session command history. This will prevent growing memory consumption of a long-running session and allows pooled connections to MaxScale to be used. The drawback of this is the fact that if a server goes down, the session state will not be consistent anymore.|
|refresh_databases|true, false|Enable database map refreshing mid-session. These are triggered by a failure to change the database i.e. `USE ...``queries.| |refresh_databases|true, false|Enable database map refreshing mid-session. These are triggered by a failure to change the database i.e. `USE ...``queries.|
|refresh_interval|float|The minimum interval between database map refreshes in seconds.| |refresh_interval|float|The minimum interval between database map refreshes in seconds.|
|ignore_databases|string|List of databases to ignore when checking for duplicate databases.|
|ignore_databases_regex|string|Regular expression that is matched against database names when checking for duplicate databases.|
## Limitations ## Limitations
The schemarouter router currently has some limitations due to the nature of the sharding implementation and the way the session variables are detected and routed. Here is a list of the current limitations. The schemarouter router currently has some limitations due to the nature of the sharding implementation and the way the session variables are detected and routed. Here is a list of the current limitations.