github-mirrors/elasticsearch
1
0
Fork 0
mirror of https://github.com/elastic/elasticsearch.git synced 2025-06-29 01:44:36 -04:00
Code Issues Projects Releases Packages Wiki Activity

[DOCS] Fix typos in flattened field type docs

Browse source
This commit is contained in:
James Rodewig 2021-10-05 14:14:29 -04:00
parent 609a7321b2
commit dbb8a015ad
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/reference/mapping/types/flattened.asciidoc
View file

@ -29,7 +29,7 @@ document content, as it treats all values as keywords and does not provide full
search functionality. The default approach, where each subfield has its own search functionality. The default approach, where each subfield has its own
entry in the mappings, works well in the majority of cases. entry in the mappings, works well in the majority of cases.
An flattened object field can be created as follows: A flattened object field can be created as follows:
[source,console] [source,console]
-------------------------------- --------------------------------
@ -112,7 +112,7 @@ When querying, it is not possible to refer to field keys using wildcards, as in
`range`, treat the values as string keywords. Highlighting is not supported on `range`, treat the values as string keywords. Highlighting is not supported on
`flattened` fields. `flattened` fields.
It is possible to sort on an flattened object field, as well as perform simple It is possible to sort on a flattened object field, as well as perform simple
keyword-style aggregations such as `terms`. As with queries, there is no keyword-style aggregations such as `terms`. As with queries, there is no
special support for numerics -- all values in the JSON object are treated as special support for numerics -- all values in the JSON object are treated as
keywords. When sorting, this implies that values are compared keywords. When sorting, this implies that values are compared