From ffd52ae52bf77745357141aa88fdf794f804779d Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Thu, 11 Jun 2015 17:01:02 +0300 Subject: [PATCH] Fixed documentation. --- Routers/SchemaRouter.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Routers/SchemaRouter.md b/Routers/SchemaRouter.md index 4f3cc4966..951eed6b5 100644 --- a/Routers/SchemaRouter.md +++ b/Routers/SchemaRouter.md @@ -46,10 +46,10 @@ The schemarouter supports the following router options: |option |parameter |description| |-------------------|-----------|-----------| -|max_sescmd_hitory | |Set a limit on the number of session modifying commands a session can execute. This sets an effective cap on the memory consupmtion of the session.| -|disable_sescmd_history||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_interval||The minimum interval between database map refreshes in seconds. +|max_sescmd_hitory |integer |Set a limit on the number of session modifying commands a session can execute. This sets an effective cap on the memory consupmtion of the session.| +|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_interval|float|The minimum interval between database map refreshes in seconds.| ## 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.