From 1bcc73666ab2ff32fb5d2379ca731cdf91354dbd Mon Sep 17 00:00:00 2001 From: Niclas Antti Date: Wed, 12 Aug 2020 11:24:23 +0300 Subject: [PATCH] Fix some incorrect links in documentation --- Documentation/Filters/CCRFilter.md | 2 +- Documentation/Filters/Cache.md | 4 ++-- Documentation/Filters/Throttle.md | 6 +++--- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/Documentation/Filters/CCRFilter.md b/Documentation/Filters/CCRFilter.md index 26ce97df5..1672b1e8e 100644 --- a/Documentation/Filters/CCRFilter.md +++ b/Documentation/Filters/CCRFilter.md @@ -44,7 +44,7 @@ The CCR filter has no mandatory parameters. The time window during which queries are routed to the master. The duration can be specified as documented -[here](Getting-Started/Configuration-Guide.md#durations) +[here](../Getting-Started/Configuration-Guide.md#durations) but the value will always be rounded to the nearest second. If no explicit unit has been specified, the value is interpreted as seconds in MaxScale 2.4. In subsequent versions a value without a unit may be rejected. diff --git a/Documentation/Filters/Cache.md b/Documentation/Filters/Cache.md index bc3f8a94e..1d5c40dba 100644 --- a/Documentation/Filters/Cache.md +++ b/Documentation/Filters/Cache.md @@ -137,7 +137,7 @@ hard_ttl=60s The default value is `0s`, which means no limit. The duration can be specified as explained -[here](Getting-Started/Configuration-Guide.md#durations). +[here](../Getting-Started/Configuration-Guide.md#durations). If no explicit unit has been specified, the value is interpreted as seconds in MaxScale 2.4. In subsequent versions a value without a unit may be rejected. @@ -159,7 +159,7 @@ The default value is `0`, which means no limit. If the value of `soft_ttl` is larger than `hard_ttl` it will be adjusted down to the same value. The duration can be specifed as explained -[here](Getting-Started/Configuration-Guide.md#durations). +[here](../Getting-Started/Configuration-Guide.md#durations). If no explicit unit has been specified, the value is interpreted as seconds in MaxScale 2.4. In subsequent versions a value without a unit may be rejected. diff --git a/Documentation/Filters/Throttle.md b/Documentation/Filters/Throttle.md index 5cc3c4299..7c858f18b 100644 --- a/Documentation/Filters/Throttle.md +++ b/Documentation/Filters/Throttle.md @@ -77,7 +77,7 @@ This defines how long a session is allowed to be throttled before MaxScale disconnects the session. The value is specified as documented -[here](Getting-Started/Configuration-Guide.md#durations). +[here](../Getting-Started/Configuration-Guide.md#durations). If no explicit unit is provided, the value is interpreted as milliseconds in MaxScale 2.4. In subsequent versions a value without a unit may be rejected. @@ -96,7 +96,7 @@ Due to the underlying granularity of time measurment (as of June 2018), it is not recommended that this value is set to less than 100 milliseconds. The value is specified as documented -[here](Getting-Started/Configuration-Guide.md#durations). +[here](../Getting-Started/Configuration-Guide.md#durations). If no explicit unit is provided, the value is interpreted as milliseconds in MaxScale 2.4. In subsequent versions a value without a unit may be rejected. @@ -109,6 +109,6 @@ starts as soon as the filter throttles the frequency. Continuous throttling ends when no throttling has been performed in the past `continuous_duration` time. The value is specified as documented -[here](Getting-Started/Configuration-Guide.md#durations). +[here](../Getting-Started/Configuration-Guide.md#durations). If no explicit unit is provided, the value is interpreted as milliseconds in MaxScale 2.4. In subsequent versions a value without a unit may be rejected.