You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of Redis Community Edition 8.0, configuration parameters for the time series data structure are now set in the following ways:
20
+
{{< note >}}
21
+
As of Redis Community Edition (CE) 8.0, configuration parameters for the time series data structure are now set in the following ways:
22
22
* At load time via your `redis.conf` file.
23
23
* At run time (where applicable) using the [`CONFIG SET`]({{< relref "/commands/config-set" >}}) command.
24
24
25
-
Also, Redis CE 8.0 persists probabilistic configuration parameters just like any other configuration parameters (e.g., using the [`CONFIG REWRITE`]({{< baseurl >}}/commands/config-rewrite/) command).
25
+
Also, CE 8.0 persists probabilistic configuration parameters just like any other configuration parameters (e.g., using the [`CONFIG REWRITE`]({{< baseurl >}}/commands/config-rewrite/) command).
26
26
{{< /note >}}
27
27
28
28
## Redis Query Engine configuration parameters
@@ -39,28 +39,27 @@ The following table summarizes which configuration parameters can be set at run-
If present, load the custom Chinese dictionary from the specified path. See [Using custom dictionaries]({{< baseurl >}}/develop/interact/search-and-query/advanced-concepts/chinese#using-custom-dictionaries) for more details.
215
215
216
216
Type: string
217
217
218
218
Default: not set
219
219
220
-
### search-gc-policy
220
+
### GC_POLICY
221
221
222
222
The garbage collection policy. The two supported policies are:
223
223
* FORK: uses a forked thread for garbage collection (v1.4.1 and above). This is the default GC policy since v1.6.1 and is ideal for general purpose workloads.
224
224
* LEGACY: uses a synchronous, in-process fork. This is ideal for read-heavy and append-heavy workloads with very few updates/deletes. Deprecated in v2.6.0.
225
225
226
-
Note: When `search-gc-policy` is set to `FORK`, it can be combined with the `search-fork-gc-run-interval` and `search-fork-gc-retry-interval` settings.
226
+
Note: When `GC_POLICY` is set to `FORK`, it can be combined with the `search-fork-gc-run-interval` and `search-fork-gc-retry-interval` settings.
227
227
228
228
Type: string
229
229
230
230
Valid values: `FORK` or `DEFAULT`
231
231
232
232
Default: `FORK`
233
233
234
-
### search-gc-scansize
234
+
### search-gc-scan-size
235
235
236
236
The bulk size of the internal GC used for cleaning up indexes.
Copy file name to clipboardExpand all lines: content/develop/interact/search-and-query/advanced-concepts/dialects.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,10 +15,13 @@ title: Query dialects
15
15
weight: 5
16
16
---
17
17
18
-
Redis Community Edition currently supports four query dialects for use with the [`FT.SEARCH`]({{< baseurl >}}/commands/ft.search/), [`FT.AGGREGATE`]({{< baseurl >}}/commands/ft.aggregate/), and other Redis Query Engine commands.
18
+
Redis Community Edition (CE) currently supports four query dialects for use with the [`FT.SEARCH`]({{< baseurl >}}/commands/ft.search/), [`FT.AGGREGATE`]({{< baseurl >}}/commands/ft.aggregate/), and other Redis Query Engine commands.
19
19
Dialects provide for enhancing the query API incrementally, introducing innovative behaviors and new features that support new use cases in a way that does not break the API for existing applications.
20
20
21
-
## `DIALECT 1`
21
+
{{< note >}}Dialects 1, 3, and 4 are deprecated in CE version 8. However, DIALECT 1 remains the default.
22
+
{{< /note >}}
23
+
24
+
## `DIALECT 1` (Deprecated)
22
25
23
26
Dialect version 1 was the default query syntax dialect from the first release of search and query until dialect version 2 was introduced with version [2.4](https://github.com/RediSearch/RediSearch/releases/tag/v2.4.3).
24
27
This dialect is also the default dialect. See below for information about changing the default dialect.
@@ -124,7 +127,7 @@ The Dialect version 2 enhancements also introduce simplified syntax for logical
Dialect version 3 was introduced in the [2.6](https://github.com/RediSearch/RediSearch/releases/tag/v2.6.3) release. This version introduced support for multi-value indexing and querying of attributes for any attribute type ( [TEXT]({{< baseurl >}}/develop/interact/search-and-query/indexing/#index-json-arrays-as-text), [TAG]({{< baseurl >}}/develop/interact/search-and-query/indexing/#index-json-arrays-as-tag), [NUMERIC]({{< baseurl >}}/develop/interact/search-and-query/indexing/#index-json-arrays-as-numeric), [GEO]({{< baseurl >}}/develop/interact/search-and-query/indexing/#index-json-arrays-as-geo) and [VECTOR]({{< baseurl >}}/develop/interact/search-and-query/indexing/#index-json-arrays-as-vector)) defined by a [JSONPath]({{< relref "/develop/data-types/json/path" >}}) leading to an array or multiple scalar values. Support for [GEOSHAPE]({{< relref "/develop/interact/search-and-query/query/geo-spatial" >}}) queries was also introduced in this dialect.
130
133
@@ -190,7 +193,7 @@ Now search, with and without `DIALECT 3`.
190
193
DIALECT 3 is required for shape-based (`POINT` or `POLYGON`) geospatial queries.
191
194
{{% /alert %}}
192
195
193
-
## `DIALECT 4`
196
+
## `DIALECT 4` (Deprecated)
194
197
195
198
Dialect version 4 was introduced in the [2.8](https://github.com/RediSearch/RediSearch/releases/tag/v2.8.4) release. It introduces performance optimizations for sorting operations on [`FT.SEARCH`]({{< baseurl >}}/commands/ft.search/) and [`FT.AGGREGATE`]({{< baseurl >}}/commands/ft.aggregate/). Apart from specifying `DIALECT 4` at the end of a [`FT.SEARCH`]({{< baseurl >}}/commands/ft.search/) command, there are no other syntactic changes. Dialect version 1 remains the default dialect. To use dialect version 4, append `DIALECT 4` to your query command.
0 commit comments