From 105b5a0b5b2c71f19a39c9b0d21cb88c3b71b118 Mon Sep 17 00:00:00 2001 From: Sarolta Hoblik Date: Mon, 27 Jan 2025 16:27:51 +0100 Subject: [PATCH] Fix typo in tutorial --- docs/reference/quickstart/full-text-filtering-tutorial.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/quickstart/full-text-filtering-tutorial.asciidoc b/docs/reference/quickstart/full-text-filtering-tutorial.asciidoc index b602ee5076434..05c48813c110f 100644 --- a/docs/reference/quickstart/full-text-filtering-tutorial.asciidoc +++ b/docs/reference/quickstart/full-text-filtering-tutorial.asciidoc @@ -107,7 +107,7 @@ PUT /cooking_blog/_mapping <1> The `standard` analyzer is used by default for `text` fields if an `analyzer` isn't specified. It's included here for demonstration purposes. <2> <> are used here to index `text` fields as both `text` and `keyword` <>. This enables both full-text search and exact matching/filtering on the same field. Note that if you used <>, these multi-fields would be created automatically. -<3> The <> prevents indexing values longer than 256 characters in the `keyword` field. Again this is the default value, but it's included here for for demonstration purposes. +<3> The <> prevents indexing values longer than 256 characters in the `keyword` field. Again this is the default value, but it's included here for demonstration purposes. It helps to save disk space and avoid potential issues with Lucene's term byte-length limit. [TIP]