Skip to content
This repository was archived by the owner on Sep 21, 2021. It is now read-only.

Commit 097e422

Browse files
committed
Edited 052_Mapping_Analysis/50_Complex_datatypes.asciidoc with Atlas code editor
1 parent 6bcfb2e commit 097e422

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

052_Mapping_Analysis/50_Complex_datatypes.asciidoc

+4-2
Original file line numberDiff line numberDiff line change
@@ -26,15 +26,17 @@ a new field by indexing an array, Elasticsearch will use the
2626
datatype of the first value in the array to determine the `type` of the
2727
new field.
2828

29-
NOTE: When you get a document back from Elasticsearch, any arrays will be in the
29+
[NOTE]
30+
====
31+
When you get a document back from Elasticsearch, any arrays will be in the
3032
same order as when you indexed the document. The `_source` field that you get
3133
back contains exactly the same JSON document that you indexed.
3234
3335
However, arrays are _indexed_—made searchable--as multivalue fields,
3436
which are unordered. ((("indexing", "of arrays")))((("arrays", "indexed as multi-value fields"))) At search time, you can't refer to ``the first element''
3537
or ``the last element.'' Rather, think of an array as a _bag of values_.
3638
((("arrays", "empty")))
37-
39+
====
3840

3941
==== Empty Fields
4042

0 commit comments

Comments
 (0)