From 6d26e5f6293c72a61ef4ee6798ec30d89e99e353 Mon Sep 17 00:00:00 2001 From: Salvatore Campagna Date: Thu, 29 Aug 2024 16:31:29 +0200 Subject: [PATCH 1/8] docs: update synthetic source docs --- docs/reference/mapping/types/date_nanos.asciidoc | 3 +-- docs/reference/mapping/types/keyword.asciidoc | 2 +- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/reference/mapping/types/date_nanos.asciidoc b/docs/reference/mapping/types/date_nanos.asciidoc index 1a3b390b1690c..3799426c6881b 100644 --- a/docs/reference/mapping/types/date_nanos.asciidoc +++ b/docs/reference/mapping/types/date_nanos.asciidoc @@ -152,8 +152,7 @@ of official GA features. `date_nanos` fields support <> in their default configuration. Synthetic `_source` cannot be used together with -<>, <> set to true -or with <> disabled. +<> or with <> disabled. Synthetic source always sorts `date_nanos` fields. For example: [source,console,id=synthetic-source-date-nanos-example] diff --git a/docs/reference/mapping/types/keyword.asciidoc b/docs/reference/mapping/types/keyword.asciidoc index 59d307c4df0ad..7f5ba1b20481f 100644 --- a/docs/reference/mapping/types/keyword.asciidoc +++ b/docs/reference/mapping/types/keyword.asciidoc @@ -181,7 +181,7 @@ of official GA features. `keyword` fields support <> in their default configuration. Synthetic `_source` cannot be used together with -a <> or <>. +<>. By default, synthetic source sorts `keyword` fields and removes duplicates. For example: From 0895a7675809a9b1074a3271c6a33694e48b7b4f Mon Sep 17 00:00:00 2001 From: Salvatore Campagna Date: Thu, 29 Aug 2024 16:38:10 +0200 Subject: [PATCH 2/8] fix: also doc values false works --- docs/reference/mapping/types/date_nanos.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/mapping/types/date_nanos.asciidoc b/docs/reference/mapping/types/date_nanos.asciidoc index 3799426c6881b..5af818a59b35c 100644 --- a/docs/reference/mapping/types/date_nanos.asciidoc +++ b/docs/reference/mapping/types/date_nanos.asciidoc @@ -152,7 +152,7 @@ of official GA features. `date_nanos` fields support <> in their default configuration. Synthetic `_source` cannot be used together with -<> or with <> disabled. +<>. Synthetic source always sorts `date_nanos` fields. For example: [source,console,id=synthetic-source-date-nanos-example] From f49513d4510e5d2b3fee90dac0cdcb76111a473d Mon Sep 17 00:00:00 2001 From: Salvatore Campagna Date: Thu, 29 Aug 2024 16:42:08 +0200 Subject: [PATCH 3/8] Revert "fix: also doc values false works" This reverts commit 0895a7675809a9b1074a3271c6a33694e48b7b4f. --- docs/reference/mapping/types/date_nanos.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/mapping/types/date_nanos.asciidoc b/docs/reference/mapping/types/date_nanos.asciidoc index 5af818a59b35c..3799426c6881b 100644 --- a/docs/reference/mapping/types/date_nanos.asciidoc +++ b/docs/reference/mapping/types/date_nanos.asciidoc @@ -152,7 +152,7 @@ of official GA features. `date_nanos` fields support <> in their default configuration. Synthetic `_source` cannot be used together with -<>. +<> or with <> disabled. Synthetic source always sorts `date_nanos` fields. For example: [source,console,id=synthetic-source-date-nanos-example] From 4ac107da4a4a63c897c7624eb2d00a8903ddef3d Mon Sep 17 00:00:00 2001 From: Salvatore Campagna Date: Thu, 17 Oct 2024 15:49:30 +0200 Subject: [PATCH 4/8] fix: update synthetic source documentation --- docs/plugins/mapper-annotated-text.asciidoc | 5 ----- docs/reference/how-to/knn-search.asciidoc | 3 --- docs/reference/mapping/types/binary.asciidoc | 2 +- docs/reference/mapping/types/boolean.asciidoc | 3 +-- docs/reference/mapping/types/date.asciidoc | 3 +-- docs/reference/mapping/types/date_nanos.asciidoc | 3 +-- docs/reference/mapping/types/flattened.asciidoc | 3 +-- docs/reference/mapping/types/geo-point.asciidoc | 3 +-- docs/reference/mapping/types/histogram.asciidoc | 2 +- docs/reference/mapping/types/ip.asciidoc | 3 +-- docs/reference/mapping/types/keyword.asciidoc | 3 +-- docs/reference/mapping/types/range.asciidoc | 2 +- docs/reference/mapping/types/search-as-you-type.asciidoc | 3 +-- docs/reference/mapping/types/text.asciidoc | 4 ---- docs/reference/mapping/types/token-count.asciidoc | 3 +-- docs/reference/mapping/types/version.asciidoc | 4 ++-- docs/reference/mapping/types/wildcard.asciidoc | 4 ++-- 17 files changed, 16 insertions(+), 37 deletions(-) diff --git a/docs/plugins/mapper-annotated-text.asciidoc b/docs/plugins/mapper-annotated-text.asciidoc index 9b6eccd136696..956b6bedffff1 100644 --- a/docs/plugins/mapper-annotated-text.asciidoc +++ b/docs/plugins/mapper-annotated-text.asciidoc @@ -155,11 +155,6 @@ be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. -`annotated_text` fields support {ref}/mapping-source-field.html#synthetic-source[synthetic `_source`] if they have -a {ref}/keyword.html#keyword-synthetic-source[`keyword`] sub-field that supports synthetic -`_source` or if the `annotated_text` field sets `store` to `true`. Either way, it may -not have {ref}/copy-to.html[`copy_to`]. - If using a sub-`keyword` field then the values are sorted in the same way as a `keyword` field's values are sorted. By default, that means sorted with duplicates removed. So: diff --git a/docs/reference/how-to/knn-search.asciidoc b/docs/reference/how-to/knn-search.asciidoc index 18882380ce160..a8697eea27619 100644 --- a/docs/reference/how-to/knn-search.asciidoc +++ b/docs/reference/how-to/knn-search.asciidoc @@ -59,9 +59,6 @@ since it relies on separate data structures to perform the search. Before using the <> parameter, make sure to review the downsides of omitting fields from `_source`. -Another option is to use <> if all -your index fields support it. - [discrete] === Ensure data nodes have enough memory diff --git a/docs/reference/mapping/types/binary.asciidoc b/docs/reference/mapping/types/binary.asciidoc index a06e5b4f572e0..6ce31edfa8ab0 100644 --- a/docs/reference/mapping/types/binary.asciidoc +++ b/docs/reference/mapping/types/binary.asciidoc @@ -63,7 +63,7 @@ be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. -`binary` fields support <> only when <> are enabled. Synthetic source always sorts `binary` values in order of their byte representation. For example: +Synthetic source always sorts `binary` values in order of their byte representation. For example: [source,console,id=synthetic-source-binary-example] ---- PUT idx diff --git a/docs/reference/mapping/types/boolean.asciidoc b/docs/reference/mapping/types/boolean.asciidoc index 494c41021dd2a..7714d3e7c383d 100644 --- a/docs/reference/mapping/types/boolean.asciidoc +++ b/docs/reference/mapping/types/boolean.asciidoc @@ -241,8 +241,7 @@ any issues, but features in technical preview are not subject to the support SLA of official GA features. `boolean` fields support <> in their -default configuration. Synthetic `_source` cannot be used together with -<> or with <> disabled. +default configuration. Synthetic source always sorts `boolean` fields. For example: [source,console,id=synthetic-source-boolean-example] diff --git a/docs/reference/mapping/types/date.asciidoc b/docs/reference/mapping/types/date.asciidoc index 53b17a669ae75..0e08f148dce26 100644 --- a/docs/reference/mapping/types/date.asciidoc +++ b/docs/reference/mapping/types/date.asciidoc @@ -240,8 +240,7 @@ any issues, but features in technical preview are not subject to the support SLA of official GA features. `date` fields support <> in their -default configuration. Synthetic `_source` cannot be used together with -<> or with <> disabled. +default configuration. Synthetic source always sorts `date` fields. For example: [source,console,id=synthetic-source-date-example] diff --git a/docs/reference/mapping/types/date_nanos.asciidoc b/docs/reference/mapping/types/date_nanos.asciidoc index 901b9afb668b1..c4a8fb2a2b1fc 100644 --- a/docs/reference/mapping/types/date_nanos.asciidoc +++ b/docs/reference/mapping/types/date_nanos.asciidoc @@ -151,8 +151,7 @@ any issues, but features in technical preview are not subject to the support SLA of official GA features. `date_nanos` fields support <> in their -default configuration. Synthetic `_source` cannot be used together with -<> or with <> disabled. +default configuration. Synthetic source always sorts `date_nanos` fields. For example: [source,console,id=synthetic-source-date-nanos-example] diff --git a/docs/reference/mapping/types/flattened.asciidoc b/docs/reference/mapping/types/flattened.asciidoc index af6ef3e739d0f..a4ad19edf5d4f 100644 --- a/docs/reference/mapping/types/flattened.asciidoc +++ b/docs/reference/mapping/types/flattened.asciidoc @@ -325,8 +325,7 @@ any issues, but features in technical preview are not subject to the support SLA of official GA features. Flattened fields support <> in their default -configuration. Synthetic `_source` cannot be used with <> -disabled. +configuration. Synthetic source always sorts alphabetically and de-duplicates flattened fields. For example: diff --git a/docs/reference/mapping/types/geo-point.asciidoc b/docs/reference/mapping/types/geo-point.asciidoc index 9ba8ea6e46782..b3f2bc6c21d44 100644 --- a/docs/reference/mapping/types/geo-point.asciidoc +++ b/docs/reference/mapping/types/geo-point.asciidoc @@ -220,8 +220,7 @@ any issues, but features in technical preview are not subject to the support SLA of official GA features. `geo_point` fields support <> in their -default configuration. Synthetic `_source` cannot be used together with <> or with -<> disabled. +default configuration. Synthetic source always sorts `geo_point` fields (first by latitude and then longitude) and reduces them to their stored precision. For example: diff --git a/docs/reference/mapping/types/histogram.asciidoc b/docs/reference/mapping/types/histogram.asciidoc index 8cd30110250bf..cdebe97000d68 100644 --- a/docs/reference/mapping/types/histogram.asciidoc +++ b/docs/reference/mapping/types/histogram.asciidoc @@ -79,7 +79,7 @@ any issues, but features in technical preview are not subject to the support SLA of official GA features. `histogram` fields support <> in their -default configuration. Synthetic `_source` cannot be used together with <>. +default configuration. NOTE: To save space, zero-count buckets are not stored in the histogram doc values. As a result, when indexing a histogram field in an index with synthetic source enabled, diff --git a/docs/reference/mapping/types/ip.asciidoc b/docs/reference/mapping/types/ip.asciidoc index f85dd78ecbd4a..5ce541d456637 100644 --- a/docs/reference/mapping/types/ip.asciidoc +++ b/docs/reference/mapping/types/ip.asciidoc @@ -162,8 +162,7 @@ any issues, but features in technical preview are not subject to the support SLA of official GA features. `ip` fields support <> in their default -configuration. Synthetic `_source` cannot be used together with -<> or with <> disabled. +configuration. Synthetic source always sorts `ip` fields and removes duplicates. For example: [source,console,id=synthetic-source-ip-example] diff --git a/docs/reference/mapping/types/keyword.asciidoc b/docs/reference/mapping/types/keyword.asciidoc index c49ce2507acab..c7a79cd1c17d6 100644 --- a/docs/reference/mapping/types/keyword.asciidoc +++ b/docs/reference/mapping/types/keyword.asciidoc @@ -179,8 +179,7 @@ any issues, but features in technical preview are not subject to the support SLA of official GA features. `keyword` fields support <> in their -default configuration. Synthetic `_source` cannot be used together with -<>. +default configuration. By default, synthetic source sorts `keyword` fields and removes duplicates. For example: diff --git a/docs/reference/mapping/types/range.asciidoc b/docs/reference/mapping/types/range.asciidoc index 04341f68c630a..628480cb78503 100644 --- a/docs/reference/mapping/types/range.asciidoc +++ b/docs/reference/mapping/types/range.asciidoc @@ -247,7 +247,7 @@ any issues, but features in technical preview are not subject to the support SLA of official GA features. `range` fields support <> in their default -configuration. Synthetic `_source` cannot be used with <> disabled. +configuration. Synthetic source always sorts values and removes duplicates for all `range` fields except `ip_range`. Ranges are sorted by their lower bound and then by upper bound. For example: [source,console,id=synthetic-source-range-sorting-example] diff --git a/docs/reference/mapping/types/search-as-you-type.asciidoc b/docs/reference/mapping/types/search-as-you-type.asciidoc index c0bdc75f13392..3c71389f4cebb 100644 --- a/docs/reference/mapping/types/search-as-you-type.asciidoc +++ b/docs/reference/mapping/types/search-as-you-type.asciidoc @@ -266,5 +266,4 @@ any issues, but features in technical preview are not subject to the support SLA of official GA features. `search_as_you_type` fields support <> in their -default configuration. Synthetic `_source` cannot be used together with -<>. +default configuration. diff --git a/docs/reference/mapping/types/text.asciidoc b/docs/reference/mapping/types/text.asciidoc index ca69c93e8f1a8..b10484fc5ded8 100644 --- a/docs/reference/mapping/types/text.asciidoc +++ b/docs/reference/mapping/types/text.asciidoc @@ -134,10 +134,6 @@ The following parameters are accepted by `text` fields: Whether the field value should be stored and retrievable separately from the <> field. Accepts `true` or `false` (default). - This parameter will be automatically set to `true` for TSDB indices - (indices that have `index.mode` set to `time_series`) - if there is no <> - sub-field that supports synthetic `_source`. <>:: diff --git a/docs/reference/mapping/types/token-count.asciidoc b/docs/reference/mapping/types/token-count.asciidoc index 7d9dffcc82082..2e5bd111122c8 100644 --- a/docs/reference/mapping/types/token-count.asciidoc +++ b/docs/reference/mapping/types/token-count.asciidoc @@ -103,5 +103,4 @@ any issues, but features in technical preview are not subject to the support SLA of official GA features. `token_count` fields support <> in their -default configuration. Synthetic `_source` cannot be used together with -<>. +default configuration. diff --git a/docs/reference/mapping/types/version.asciidoc b/docs/reference/mapping/types/version.asciidoc index 1600451432bd8..7861fa2926384 100644 --- a/docs/reference/mapping/types/version.asciidoc +++ b/docs/reference/mapping/types/version.asciidoc @@ -77,8 +77,8 @@ be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. -`version` fields support <> so long as they don't -declare <>. +`version` fields support <> in their +default configuration.. Synthetic source always sorts `version` fields and removes duplicates. For example: [source,console,id=synthetic-source-version-example] diff --git a/docs/reference/mapping/types/wildcard.asciidoc b/docs/reference/mapping/types/wildcard.asciidoc index 89a3109a37164..03fb31671c06c 100644 --- a/docs/reference/mapping/types/wildcard.asciidoc +++ b/docs/reference/mapping/types/wildcard.asciidoc @@ -133,8 +133,8 @@ The following parameters are accepted by `wildcard` fields: [[wildcard-synthetic-source]] ==== Synthetic `_source` -`wildcard` fields support <> so long as they don't -declare <>. +`wildcard` fields support <> in their +default configuration.. Synthetic source always sorts `wildcard` fields. For example: [source,console,id=synthetic-source-wildcard-example] From 1b62bfab233199732fa35901e2cf495d5220d27c Mon Sep 17 00:00:00 2001 From: Salvatore Campagna Date: Thu, 17 Oct 2024 16:05:11 +0200 Subject: [PATCH 5/8] fix: all field types support it --- docs/reference/how-to/knn-search.asciidoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/reference/how-to/knn-search.asciidoc b/docs/reference/how-to/knn-search.asciidoc index a8697eea27619..1d9c988f7b6c9 100644 --- a/docs/reference/how-to/knn-search.asciidoc +++ b/docs/reference/how-to/knn-search.asciidoc @@ -59,6 +59,8 @@ since it relies on separate data structures to perform the search. Before using the <> parameter, make sure to review the downsides of omitting fields from `_source`. +Another option is to use <>. + [discrete] === Ensure data nodes have enough memory From c2aff982db42ed4dbce54b319a06c41003d119c9 Mon Sep 17 00:00:00 2001 From: Salvatore Campagna Date: Thu, 17 Oct 2024 16:14:03 +0200 Subject: [PATCH 6/8] fix: no need to explicitly mention it --- docs/reference/mapping/types/aggregate-metric-double.asciidoc | 3 --- docs/reference/mapping/types/date.asciidoc | 3 --- docs/reference/mapping/types/date_nanos.asciidoc | 3 --- docs/reference/mapping/types/geo-point.asciidoc | 3 --- docs/reference/mapping/types/geo-shape.asciidoc | 3 --- docs/reference/mapping/types/ip.asciidoc | 3 --- docs/reference/mapping/types/keyword.asciidoc | 3 --- docs/reference/mapping/types/wildcard.asciidoc | 2 -- 8 files changed, 23 deletions(-) diff --git a/docs/reference/mapping/types/aggregate-metric-double.asciidoc b/docs/reference/mapping/types/aggregate-metric-double.asciidoc index 8a4ddffc30bbd..faae5118e42bb 100644 --- a/docs/reference/mapping/types/aggregate-metric-double.asciidoc +++ b/docs/reference/mapping/types/aggregate-metric-double.asciidoc @@ -259,9 +259,6 @@ be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. -`aggregate_metric-double` fields support <> in their default -configuration. - For example: [source,console,id=synthetic-source-aggregate-metric-double-example] ---- diff --git a/docs/reference/mapping/types/date.asciidoc b/docs/reference/mapping/types/date.asciidoc index 0e08f148dce26..fe6c84908d650 100644 --- a/docs/reference/mapping/types/date.asciidoc +++ b/docs/reference/mapping/types/date.asciidoc @@ -239,9 +239,6 @@ be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. -`date` fields support <> in their -default configuration. - Synthetic source always sorts `date` fields. For example: [source,console,id=synthetic-source-date-example] ---- diff --git a/docs/reference/mapping/types/date_nanos.asciidoc b/docs/reference/mapping/types/date_nanos.asciidoc index c4a8fb2a2b1fc..f2e75acd7ed8f 100644 --- a/docs/reference/mapping/types/date_nanos.asciidoc +++ b/docs/reference/mapping/types/date_nanos.asciidoc @@ -150,9 +150,6 @@ be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. -`date_nanos` fields support <> in their -default configuration. - Synthetic source always sorts `date_nanos` fields. For example: [source,console,id=synthetic-source-date-nanos-example] ---- diff --git a/docs/reference/mapping/types/geo-point.asciidoc b/docs/reference/mapping/types/geo-point.asciidoc index b3f2bc6c21d44..10ae463cdfca7 100644 --- a/docs/reference/mapping/types/geo-point.asciidoc +++ b/docs/reference/mapping/types/geo-point.asciidoc @@ -219,9 +219,6 @@ be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. -`geo_point` fields support <> in their -default configuration. - Synthetic source always sorts `geo_point` fields (first by latitude and then longitude) and reduces them to their stored precision. For example: [source,console,id=synthetic-source-geo-point-example] diff --git a/docs/reference/mapping/types/geo-shape.asciidoc b/docs/reference/mapping/types/geo-shape.asciidoc index e50c7d73b1b76..affebc6f721e4 100644 --- a/docs/reference/mapping/types/geo-shape.asciidoc +++ b/docs/reference/mapping/types/geo-shape.asciidoc @@ -502,6 +502,3 @@ synthetic `_source` is in technical preview. Features in technical preview may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. - -`geo_shape` fields support <> in their -default configuration. diff --git a/docs/reference/mapping/types/ip.asciidoc b/docs/reference/mapping/types/ip.asciidoc index 5ce541d456637..43dad91d916da 100644 --- a/docs/reference/mapping/types/ip.asciidoc +++ b/docs/reference/mapping/types/ip.asciidoc @@ -161,9 +161,6 @@ be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. -`ip` fields support <> in their default -configuration. - Synthetic source always sorts `ip` fields and removes duplicates. For example: [source,console,id=synthetic-source-ip-example] ---- diff --git a/docs/reference/mapping/types/keyword.asciidoc b/docs/reference/mapping/types/keyword.asciidoc index c7a79cd1c17d6..c01ff276246a8 100644 --- a/docs/reference/mapping/types/keyword.asciidoc +++ b/docs/reference/mapping/types/keyword.asciidoc @@ -178,9 +178,6 @@ be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. -`keyword` fields support <> in their -default configuration. - By default, synthetic source sorts `keyword` fields and removes duplicates. For example: [source,console,id=synthetic-source-keyword-example-default] diff --git a/docs/reference/mapping/types/wildcard.asciidoc b/docs/reference/mapping/types/wildcard.asciidoc index 03fb31671c06c..a52f281657c6f 100644 --- a/docs/reference/mapping/types/wildcard.asciidoc +++ b/docs/reference/mapping/types/wildcard.asciidoc @@ -133,8 +133,6 @@ The following parameters are accepted by `wildcard` fields: [[wildcard-synthetic-source]] ==== Synthetic `_source` -`wildcard` fields support <> in their -default configuration.. Synthetic source always sorts `wildcard` fields. For example: [source,console,id=synthetic-source-wildcard-example] From e16002c16c34f5b1c81c5d01b53e02d94a511012 Mon Sep 17 00:00:00 2001 From: Salvatore Campagna Date: Fri, 18 Oct 2024 10:24:16 +0200 Subject: [PATCH 7/8] fix: synthetic source sorting --- docs/reference/mapping/types/binary.asciidoc | 2 +- docs/reference/mapping/types/boolean.asciidoc | 2 +- docs/reference/mapping/types/date.asciidoc | 2 +- docs/reference/mapping/types/date_nanos.asciidoc | 2 +- docs/reference/mapping/types/flattened.asciidoc | 2 +- docs/reference/mapping/types/geo-point.asciidoc | 2 +- docs/reference/mapping/types/ip.asciidoc | 2 +- docs/reference/mapping/types/keyword.asciidoc | 2 +- docs/reference/mapping/types/numeric.asciidoc | 2 +- docs/reference/mapping/types/range.asciidoc | 2 +- docs/reference/mapping/types/version.asciidoc | 2 +- docs/reference/mapping/types/wildcard.asciidoc | 2 +- 12 files changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/reference/mapping/types/binary.asciidoc b/docs/reference/mapping/types/binary.asciidoc index 6ce31edfa8ab0..5733a28eb711a 100644 --- a/docs/reference/mapping/types/binary.asciidoc +++ b/docs/reference/mapping/types/binary.asciidoc @@ -63,7 +63,7 @@ be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. -Synthetic source always sorts `binary` values in order of their byte representation. For example: +Synthetic source may sort `binary` values in order of their byte representation. For example: [source,console,id=synthetic-source-binary-example] ---- PUT idx diff --git a/docs/reference/mapping/types/boolean.asciidoc b/docs/reference/mapping/types/boolean.asciidoc index 7714d3e7c383d..268be9016987f 100644 --- a/docs/reference/mapping/types/boolean.asciidoc +++ b/docs/reference/mapping/types/boolean.asciidoc @@ -243,7 +243,7 @@ of official GA features. `boolean` fields support <> in their default configuration. -Synthetic source always sorts `boolean` fields. For example: +Synthetic source may sort `boolean` field values. For example: [source,console,id=synthetic-source-boolean-example] ---- PUT idx diff --git a/docs/reference/mapping/types/date.asciidoc b/docs/reference/mapping/types/date.asciidoc index fe6c84908d650..4261d502ca104 100644 --- a/docs/reference/mapping/types/date.asciidoc +++ b/docs/reference/mapping/types/date.asciidoc @@ -239,7 +239,7 @@ be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. -Synthetic source always sorts `date` fields. For example: +Synthetic source may sort `date` field values. For example: [source,console,id=synthetic-source-date-example] ---- PUT idx diff --git a/docs/reference/mapping/types/date_nanos.asciidoc b/docs/reference/mapping/types/date_nanos.asciidoc index f2e75acd7ed8f..31f5ae09e7a63 100644 --- a/docs/reference/mapping/types/date_nanos.asciidoc +++ b/docs/reference/mapping/types/date_nanos.asciidoc @@ -150,7 +150,7 @@ be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. -Synthetic source always sorts `date_nanos` fields. For example: +Synthetic source may sort `date_nanos` field values. For example: [source,console,id=synthetic-source-date-nanos-example] ---- PUT idx diff --git a/docs/reference/mapping/types/flattened.asciidoc b/docs/reference/mapping/types/flattened.asciidoc index a4ad19edf5d4f..96b230794003a 100644 --- a/docs/reference/mapping/types/flattened.asciidoc +++ b/docs/reference/mapping/types/flattened.asciidoc @@ -327,7 +327,7 @@ of official GA features. Flattened fields support <> in their default configuration. -Synthetic source always sorts alphabetically and de-duplicates flattened fields. +Synthetic source may sort `flattened` field values and remove duplicates. For example: [source,console,id=synthetic-source-flattened-sorting-example] ---- diff --git a/docs/reference/mapping/types/geo-point.asciidoc b/docs/reference/mapping/types/geo-point.asciidoc index 10ae463cdfca7..0958997d3fb00 100644 --- a/docs/reference/mapping/types/geo-point.asciidoc +++ b/docs/reference/mapping/types/geo-point.asciidoc @@ -219,7 +219,7 @@ be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. -Synthetic source always sorts `geo_point` fields (first by latitude and then +Synthetic source may sort `geo_point` fields (first by latitude and then longitude) and reduces them to their stored precision. For example: [source,console,id=synthetic-source-geo-point-example] ---- diff --git a/docs/reference/mapping/types/ip.asciidoc b/docs/reference/mapping/types/ip.asciidoc index 43dad91d916da..bafc25a977caa 100644 --- a/docs/reference/mapping/types/ip.asciidoc +++ b/docs/reference/mapping/types/ip.asciidoc @@ -161,7 +161,7 @@ be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. -Synthetic source always sorts `ip` fields and removes duplicates. For example: +Synthetic source may sort `ip` field values and remove duplicates. For example: [source,console,id=synthetic-source-ip-example] ---- PUT idx diff --git a/docs/reference/mapping/types/keyword.asciidoc b/docs/reference/mapping/types/keyword.asciidoc index c01ff276246a8..554a29e891194 100644 --- a/docs/reference/mapping/types/keyword.asciidoc +++ b/docs/reference/mapping/types/keyword.asciidoc @@ -178,7 +178,7 @@ be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. -By default, synthetic source sorts `keyword` fields and removes duplicates. +Synthetic source might sort `keyword` fields and remove duplicates. For example: [source,console,id=synthetic-source-keyword-example-default] ---- diff --git a/docs/reference/mapping/types/numeric.asciidoc b/docs/reference/mapping/types/numeric.asciidoc index 5bfa1bc7c1240..2fba1931a2a29 100644 --- a/docs/reference/mapping/types/numeric.asciidoc +++ b/docs/reference/mapping/types/numeric.asciidoc @@ -254,7 +254,7 @@ All numeric fields support <>, or with <> disabled. -Synthetic source always sorts numeric fields. For example: +Synthetic source may sort numeric field values. For example: [source,console,id=synthetic-source-numeric-example] ---- PUT idx diff --git a/docs/reference/mapping/types/range.asciidoc b/docs/reference/mapping/types/range.asciidoc index 628480cb78503..3b31a1885e5b9 100644 --- a/docs/reference/mapping/types/range.asciidoc +++ b/docs/reference/mapping/types/range.asciidoc @@ -249,7 +249,7 @@ of official GA features. `range` fields support <> in their default configuration. -Synthetic source always sorts values and removes duplicates for all `range` fields except `ip_range`. Ranges are sorted by their lower bound and then by upper bound. For example: +Synthetic source may sort `range` field values and remove duplicates for all `range` fields except `ip_range`. Ranges are sorted by their lower bound and then by upper bound. For example: [source,console,id=synthetic-source-range-sorting-example] ---- PUT idx diff --git a/docs/reference/mapping/types/version.asciidoc b/docs/reference/mapping/types/version.asciidoc index 7861fa2926384..1d9f927a80ce4 100644 --- a/docs/reference/mapping/types/version.asciidoc +++ b/docs/reference/mapping/types/version.asciidoc @@ -80,7 +80,7 @@ of official GA features. `version` fields support <> in their default configuration.. -Synthetic source always sorts `version` fields and removes duplicates. For example: +Synthetic source may sort `version` field values and remove duplicates. For example: [source,console,id=synthetic-source-version-example] ---- PUT idx diff --git a/docs/reference/mapping/types/wildcard.asciidoc b/docs/reference/mapping/types/wildcard.asciidoc index a52f281657c6f..255e34ecd959b 100644 --- a/docs/reference/mapping/types/wildcard.asciidoc +++ b/docs/reference/mapping/types/wildcard.asciidoc @@ -134,7 +134,7 @@ The following parameters are accepted by `wildcard` fields: [[wildcard-synthetic-source]] ==== Synthetic `_source` -Synthetic source always sorts `wildcard` fields. For example: +Synthetic source may sort `wildcard` field values. For example: [source,console,id=synthetic-source-wildcard-example] ---- PUT idx From 7d6f6bb4b86a08d57b58b51f268997643fb2edbd Mon Sep 17 00:00:00 2001 From: Salvatore Campagna Date: Fri, 18 Oct 2024 10:52:42 +0200 Subject: [PATCH 8/8] fix: may instead of might --- docs/reference/mapping/types/keyword.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/mapping/types/keyword.asciidoc b/docs/reference/mapping/types/keyword.asciidoc index 554a29e891194..165d9d7900441 100644 --- a/docs/reference/mapping/types/keyword.asciidoc +++ b/docs/reference/mapping/types/keyword.asciidoc @@ -178,7 +178,7 @@ be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. -Synthetic source might sort `keyword` fields and remove duplicates. +Synthetic source may sort `keyword` fields and remove duplicates. For example: [source,console,id=synthetic-source-keyword-example-default] ----