DOC-5391 move search & query to AI section and more

content/commands/ft.aggregate.md

@@ -260,7 +260,7 @@ groups the results in the pipeline based on one or more properties. Each group s
 
 reduces the matching results in each group into a single record, using a reduction function. For example, `COUNT` counts the number of records in the group. The reducers can have their own property names using the `AS {name}` optional argument. If a name is not given, the resulting name will be the name of the reduce function and the group properties. For example, if a name is not given to `COUNT_DISTINCT` by property `@foo`, the resulting name will be `count_distinct(@foo)`.
 
-See [Supported GROUPBY reducers]({{< relref "develop/interact/search-and-query/advanced-concepts/aggregations#supported-groupby-reducers" >}}) for more details.   
+See [Supported GROUPBY reducers]({{< relref "develop/ai/search-and-query/advanced-concepts/aggregations#supported-groupby-reducers" >}}) for more details.   
 </details>
 
 <details open>
@@ -292,7 +292,7 @@ applies a 1-to-1 transformation on one or more properties and either stores the
 `expr` is an expression that can be used to perform arithmetic operations on numeric properties, or functions that can be applied on properties depending on their types (see below), or any combination thereof. For example, `APPLY "sqrt(@foo)/log(@bar) + 5" AS baz` evaluates this expression dynamically for each record in the pipeline and store the result as a new property called `baz`, which can be referenced by further `APPLY`/`SORTBY`/`GROUPBY`/`REDUCE` operations down the
   pipeline.
 
-See [APPLY expressions]({{< relref "develop/interact/search-and-query/advanced-concepts/aggregations/#apply-expressions" >}}) for details.
+See [APPLY expressions]({{< relref "develop/ai/search-and-query/advanced-concepts/aggregations/#apply-expressions" >}}) for details.
 </details>
 
 <details open>
@@ -316,7 +316,7 @@ filters the results using predicate expressions relating to values in each resul
 <summary><code>WITHCURSOR {COUNT} {read_size} [MAXIDLE {idle_time}]</code></summary> 
 
 Scan part of the results with a quicker alternative than `LIMIT`.
-See [Cursor API]({{< relref "develop/interact/search-and-query/advanced-concepts/aggregations#cursor-api" >}}) for more details.
+See [Cursor API]({{< relref "develop/ai/search-and-query/advanced-concepts/aggregations#cursor-api" >}}) for more details.
 </details>
 
 <details open>
@@ -336,7 +336,7 @@ You can reference parameters in the `query` by a `$`, followed by the parameter
 <details open>
 <summary><code>SCORER {scorer}</code></summary>
 
-uses a [built-in]({{< relref "/develop/interact/search-and-query/advanced-concepts/scoring" >}}) or a [user-provided]({{< relref "/develop/interact/search-and-query/administration/extensions" >}}) scoring function.
+uses a [built-in]({{< relref "/develop/ai/search-and-query/advanced-concepts/scoring" >}}) or a [user-provided]({{< relref "/develop/ai/search-and-query/administration/extensions" >}}) scoring function.
 </details>
 
 <details open>
@@ -495,6 +495,6 @@ Next, count GitHub events by user (actor), to produce the most active users.
 
 ## Related topics
 
-- [Aggregations]({{< relref "/develop/interact/search-and-query/advanced-concepts/aggregations" >}})
-- [RediSearch]({{< relref "/develop/interact/search-and-query" >}})
+- [Aggregations]({{< relref "/develop/ai/search-and-query/advanced-concepts/aggregations" >}})
+- [RediSearch]({{< relref "/develop/ai/search-and-query" >}})
 

content/commands/ft.aliasadd.md

@@ -80,4 +80,4 @@ Attempting to add the same alias returns a message that the alias already exists
 
 ## Related topics
 
-[RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+[RediSearch]({{< relref "/develop/ai/search-and-query/" >}})

content/commands/ft.aliasdel.md

@@ -66,4 +66,4 @@ OK
 
 ## Related topics
 
-[RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+[RediSearch]({{< relref "/develop/ai/search-and-query/" >}})

content/commands/ft.aliasupdate.md

@@ -68,4 +68,4 @@ OK
 
 ## Related topics
 
-[RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+[RediSearch]({{< relref "/develop/ai/search-and-query/" >}})

content/commands/ft.alter.md

@@ -102,7 +102,7 @@ OK
 
 ## Related topics
 
-- [RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+- [RediSearch]({{< relref "/develop/ai/search-and-query/" >}})
 
 
 

content/commands/ft.config-get.md

@@ -146,4 +146,4 @@ FT.CONFIG GET returns an array reply of the configuration name and value.
 
 ## Related topics
 
-[RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+[RediSearch]({{< relref "/develop/ai/search-and-query/" >}})

content/commands/ft.config-help.md

@@ -71,4 +71,4 @@ FT.CONFIG HELP returns an array reply of the configuration name and value.
 
 ## Related topics
 
-[RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+[RediSearch]({{< relref "/develop/ai/search-and-query/" >}})

content/commands/ft.config-set.md

@@ -40,7 +40,7 @@ Set the value of a RediSearch configuration parameter.
 
 Values set using `FT.CONFIG SET` are not persisted after server restart.
 
-RediSearch configuration parameters are detailed in [Configuration parameters]({{< relref "/develop/interact/search-and-query/administration/configuration" >}}).
+RediSearch configuration parameters are detailed in [Configuration parameters]({{< relref "/develop/ai/search-and-query/administration/configuration" >}}).
 
 {{% alert title="Note" color="warning" %}}
 As detailed in the link above, not all RediSearch configuration parameters can be set at runtime.
@@ -83,4 +83,4 @@ OK
 
 ## Related topics
 
-[RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+[RediSearch]({{< relref "/develop/ai/search-and-query/" >}})

content/commands/ft.create.md

@@ -222,13 +222,13 @@ after the SCHEMA keyword, declares which fields to index:
 
  - `TEXT` - Allows full-text search queries against the value in this attribute.
 
- - `TAG` - Allows exact-match queries, such as categories or primary keys, against the value in this attribute. For more information, see [Tag Fields]({{< relref "/develop/interact/search-and-query/advanced-concepts/tags" >}}).
+ - `TAG` - Allows exact-match queries, such as categories or primary keys, against the value in this attribute. For more information, see [Tag Fields]({{< relref "/develop/ai/search-and-query/advanced-concepts/tags" >}}).
 
- - `NUMERIC` - Allows numeric range queries against the value in this attribute. See [query syntax docs]({{< relref "/develop/interact/search-and-query/query/" >}}) for details on how to use numeric ranges.
+ - `NUMERIC` - Allows numeric range queries against the value in this attribute. See [query syntax docs]({{< relref "/develop/ai/search-and-query/query/" >}}) for details on how to use numeric ranges.
 
  - `GEO` - Allows radius range queries against the value (point) in this attribute. The value of the attribute must be a string containing a longitude (first) and latitude separated by a comma.
 
- - `VECTOR` - Allows vector queries against the value in this attribute. This requires [query dialect 2]({{< relref "/develop/interact/search-and-query/advanced-concepts/dialects#dialect-2" >}}) or above (introduced in [RediSearch v2.4](https://github.com/RediSearch/RediSearch/releases/tag/v2.4.3)). For more information, see [Vector Fields]({{< relref "/develop/interact/search-and-query/advanced-concepts/vectors" >}}).
+ - `VECTOR` - Allows vector queries against the value in this attribute. This requires [query dialect 2]({{< relref "/develop/ai/search-and-query/advanced-concepts/dialects#dialect-2" >}}) or above (introduced in [RediSearch v2.4](https://github.com/RediSearch/RediSearch/releases/tag/v2.4.3)). For more information, see [Vector Fields]({{< relref "/develop/ai/search-and-query/vectors" >}}).
 
  - `GEOSHAPE`- Allows polygon queries against the value in this attribute. The value of the attribute must follow a [WKT notation](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry) list of 2D points representing the polygon edges `POLYGON((x1 y1, x2 y2, ...)` separated by a comma. A `GEOSHAPE` field type can be followed by one of the following coordinate systems:
    - `SPHERICAL` for Geographic longitude and latitude coordinates
@@ -240,7 +240,7 @@ after the SCHEMA keyword, declares which fields to index:
 
  Field options are:
 
- - `SORTABLE` - `NUMERIC`, `TAG`, `TEXT`, or `GEO` attributes can have an optional **SORTABLE** argument. As the user [sorts the results by the value of this attribute]({{< relref "/develop/interact/search-and-query/advanced-concepts/sorting" >}}), the results are available with very low latency. Note that his adds memory overhead, so consider not declaring it on large text attributes. You can sort an attribute without the `SORTABLE` option, but the latency is not as good as with `SORTABLE`.
+ - `SORTABLE` - `NUMERIC`, `TAG`, `TEXT`, or `GEO` attributes can have an optional **SORTABLE** argument. As the user [sorts the results by the value of this attribute]({{< relref "/develop/ai/search-and-query/advanced-concepts/sorting" >}}), the results are available with very low latency. Note that his adds memory overhead, so consider not declaring it on large text attributes. You can sort an attribute without the `SORTABLE` option, but the latency is not as good as with `SORTABLE`.
 
  - `UNF` - By default, for hashes (not with JSON) `SORTABLE` applies a normalization to the indexed value (characters set to lowercase, removal of diacritics). When using the unnormalized form (UNF), you can disable the normalization and keep the original form of the value. With JSON, `UNF` is implicit with `SORTABLE` (normalization is disabled).
 
@@ -255,7 +255,7 @@ after the SCHEMA keyword, declares which fields to index:
    - `dm:pt` - Double metaphone for Portuguese
    - `dm:es` - Double metaphone for Spanish
 
-   For more information, see [Phonetic Matching]({{< relref "/develop/interact/search-and-query/advanced-concepts/phonetic_matching" >}}).
+   For more information, see [Phonetic Matching]({{< relref "/develop/ai/search-and-query/advanced-concepts/phonetic_matching" >}}).
 
   - `WEIGHT {weight}` for `TEXT` attributes, declares the importance of this attribute when calculating result accuracy. This is a multiplication factor, and defaults to 1 if not specified.
 
@@ -306,7 +306,7 @@ A stemmer is used for the supplied language during indexing. If an unsupported l
 Indonesian, Irish, Italian, Lithuanian, Nepali, Norwegian, Portuguese, Romanian, Russian,
 Spanish, Swedish, Tamil, Turkish, and Chinese.
 
-When adding Chinese language documents, set `LANGUAGE chinese` for the indexer to properly tokenize the terms. If you use the default language, then search terms are extracted based on punctuation characters and whitespace. The Chinese language tokenizer makes use of a segmentation algorithm (via [Friso](https://github.com/lionsoul2014/friso)), which segments text and checks it against a predefined dictionary. See [Stemming]({{< relref "/develop/interact/search-and-query/advanced-concepts/stemming" >}}) for more information.
+When adding Chinese language documents, set `LANGUAGE chinese` for the indexer to properly tokenize the terms. If you use the default language, then search terms are extracted based on punctuation characters and whitespace. The Chinese language tokenizer makes use of a segmentation algorithm (via [Friso](https://github.com/lionsoul2014/friso)), which segments text and checks it against a predefined dictionary. See [Stemming]({{< relref "/develop/ai/search-and-query/advanced-concepts/stemming" >}}) for more information.
 </details>
 
 <a name="SCORE"></a><details open>
@@ -469,9 +469,9 @@ The following example uses data similar to the hash examples above but uses JSON
 
 ## Related topics
 
-- [RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+- [RediSearch]({{< relref "/develop/ai/search-and-query/" >}})
 - [RedisJSON]({{< relref "/develop/data-types/json/" >}})
 - [Friso](https://github.com/lionsoul2014/friso)
-- [Stemming]({{< relref "/develop/interact/search-and-query/advanced-concepts/stemming" >}})
-- [Phonetic Matching]({{< relref "/develop/interact/search-and-query/advanced-concepts/phonetic_matching" >}})
+- [Stemming]({{< relref "/develop/ai/search-and-query/advanced-concepts/stemming" >}})
+- [Phonetic Matching]({{< relref "/develop/ai/search-and-query/advanced-concepts/phonetic_matching" >}})
 - [RSCoordinator](https://github.com/RedisLabsModules/RSCoordinator)

content/commands/ft.cursor-del.md

@@ -80,4 +80,4 @@ Check that the cursor is deleted.
 
 ## Related topics
 
-[RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+[RediSearch]({{< relref "/develop/ai/search-and-query/" >}})

content/commands/ft.cursor-read.md

@@ -42,7 +42,7 @@ Read next results from an existing cursor
 
 [Examples](#examples)
 
-See [Cursor API]({{< relref "develop/interact/search-and-query/advanced-concepts/aggregations#cursor-api" >}}) for more details.
+See [Cursor API]({{< relref "develop/ai/search-and-query/advanced-concepts/aggregations#cursor-api" >}}) for more details.
 
 ## Required arguments
 
@@ -84,4 +84,4 @@ FT.CURSOR READ returns an array reply where each row is an array reply and repre
 
 ## Related topics
 
-[RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+[RediSearch]({{< relref "/develop/ai/search-and-query/" >}})

content/commands/ft.dictadd.md

@@ -73,4 +73,4 @@ FT.DICTADD returns an integer reply, the number of new terms that were added.
 
 ## Related topics
 
-[RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+[RediSearch]({{< relref "/develop/ai/search-and-query/" >}})

content/commands/ft.dictdel.md

@@ -73,4 +73,4 @@ FT.DICTDEL returns an integer reply, the number of new terms that were deleted.
 
 ## Related topics
 
-[RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+[RediSearch]({{< relref "/develop/ai/search-and-query/" >}})

content/commands/ft.dictdump.md

@@ -68,6 +68,6 @@ FT.DICTDUMP returns an array, where each element is term (string).
 
 ## Related topics
 
-[RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+[RediSearch]({{< relref "/develop/ai/search-and-query/" >}})
 
 

content/commands/ft.dropindex.md

@@ -87,4 +87,4 @@ OK
 
 ## Related topics
 
-[RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+[RediSearch]({{< relref "/develop/ai/search-and-query/" >}})

content/commands/ft.explain.md

@@ -109,5 +109,5 @@ INTERSECT {
 
 ## Related topics
 
-[RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+[RediSearch]({{< relref "/develop/ai/search-and-query/" >}})
 

content/commands/ft.explaincli.md

@@ -122,5 +122,5 @@ $ redis-cli
 
 ## Related topics
 
-[RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+[RediSearch]({{< relref "/develop/ai/search-and-query/" >}})
 

content/commands/ft.info.md

@@ -360,4 +360,4 @@ The next two GC-related fields are relevant in scenarios where simultaneous chan
 
 ## Related topics
 
-[RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+[RediSearch]({{< relref "/develop/ai/search-and-query/" >}})

content/commands/ft.profile.md

@@ -405,5 +405,5 @@ Here's an example of running the `FT.PROFILE` command for a vector query.
 
 ## Related topics
 
-[RediSearch]({{< relref "/develop/interact/search-and-query/" >}})
+[RediSearch]({{< relref "/develop/ai/search-and-query/" >}})