honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[DOCS] Clarify nested type documentation

This commit is contained in:
Igor Motov 2014-03-26 11:51:19 -04:00
parent a12a36ef09
commit c2e38fbf78
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/reference/mapping/types/nested-type.asciidoc
View File

@ -37,7 +37,11 @@ instance ones), for example:
"type1" : { "type1" : {
"properties" : { "properties" : {
"obj1" : { "obj1" : {
"type" : "nested" "type" : "nested",
"properties": {
"name" : {"type": "string", "index": "not_analyzed"},
"count" : {"type": "integer"}
}
} }
} }
} }
@ -46,7 +50,8 @@ instance ones), for example:
The above will cause all `obj1` to be indexed as a nested doc. The The above will cause all `obj1` to be indexed as a nested doc. The
mapping is similar in nature to setting `type` to `object`, except that mapping is similar in nature to setting `type` to `object`, except that
it's `nested`. it's `nested`. Nested object fields can be defined explicitly as in the
example above or added dynamically in the same way as for the root object.
Note: changing an object type to nested type requires reindexing. Note: changing an object type to nested type requires reindexing.