From 6961a16b0213adf89ec949348045353cbdef1c91 Mon Sep 17 00:00:00 2001 From: "David W. Dougherty" Date: Tue, 28 May 2024 14:49:47 -0700 Subject: [PATCH] DEV: clean up old PRs from previous sites (part 3) --- content/commands/ft.alter/index.md | 2 +- content/commands/ft.dropindex/index.md | 2 +- .../basic-constructs/field-and-type-options.md | 6 +++--- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/content/commands/ft.alter/index.md b/content/commands/ft.alter/index.md index 25932abc6..4a9dc9843 100644 --- a/content/commands/ft.alter/index.md +++ b/content/commands/ft.alter/index.md @@ -81,7 +81,7 @@ contain more than 32 attributes, create it with the `MAXTEXTFIELDS` option. ## Return -FT.CREATE returns a simple string reply `OK` if executed correctly, or an error reply otherwise. +FT.ALTER returns a simple string reply `OK` if executed correctly, or an error reply otherwise. ## Examples diff --git a/content/commands/ft.dropindex/index.md b/content/commands/ft.dropindex/index.md index 333d3df3f..20669b78e 100644 --- a/content/commands/ft.dropindex/index.md +++ b/content/commands/ft.dropindex/index.md @@ -52,7 +52,7 @@ is full-text index name. You must first create the index using [`FT.CREATE`]({{<
DD -drop operation that, if set, deletes the actual document hashes. +drop index operation that, if set, deletes the actual document keys. `FT.DROPINDEX index DD` is an asynchronous operation. By default, FT.DROPINDEX does not delete the documents associated with the index. Adding the `DD` option deletes the documents as well. If an index creation is still running ([`FT.CREATE`]({{< baseurl >}}/commands/ft.create/) is running asynchronously), only the document hashes that have already been indexed are deleted. diff --git a/content/develop/interact/search-and-query/basic-constructs/field-and-type-options.md b/content/develop/interact/search-and-query/basic-constructs/field-and-type-options.md index d5437e1e0..92088c533 100644 --- a/content/develop/interact/search-and-query/basic-constructs/field-and-type-options.md +++ b/content/develop/interact/search-and-query/basic-constructs/field-and-type-options.md @@ -20,14 +20,14 @@ weight: 2 Redis Stack provides various field types that allow you to store and search different kinds of data in your indexes. This page explains the available field types, their characteristics, and how they can be used effectively. -## Number fields +## Numeric fields -Number fields are used to store non-textual, countable values. They can hold integer or floating-point values. Number fields are sortable, meaning you can perform range-based queries and retrieve documents based on specific numeric conditions. For example, you can search for documents with a price between a certain range or retrieve documents with a specific rating value. +Numeric fields are used to store non-textual, countable values. They can hold integer or floating-point values. Numeric fields are sortable, meaning you can perform range-based queries and retrieve documents based on specific numeric conditions. For example, you can search for documents with a price between a certain range or retrieve documents with a specific rating value. You can add number fields to a schema in [`FT.CREATE`]({{< baseurl >}}/commands/ft.create/) using this syntax: ``` -FT.CREATE ... SCHEMA ... {field_name} NUMBER [SORTABLE] [NOINDEX] +FT.CREATE ... SCHEMA ... {field_name} NUMERIC [SORTABLE] [NOINDEX] ``` where: