[DOCS] Fix nested root object indexing documentation

Types can no longer be specified when indexing, see:
https://github.com/elasticsearch/elasticsearch/pull/4552
This commit is contained in:
Lee Hinman 2014-07-23 16:25:36 +02:00
parent 76511158b5
commit a1a03a184c
1 changed files with 6 additions and 23 deletions

View File

@ -1,16 +1,13 @@
[[mapping-root-object-type]] [[mapping-root-object-type]]
=== Root Object Type === Root Object Type
The root object mapping is an The root object mapping is an <<mapping-object-type,object type mapping>> that
<<mapping-object-type,object type mapping>> that maps the root object (the type itself). It supports all of the different
maps the root object (the type itself). On top of all the different mappings that can be set using the <<mapping-object-type,object type mapping>>.
mappings that can be set using the
<<mapping-object-type,object type mapping>>, it
allows for additional, type level mapping definitions.
The root object mapping allows to index a JSON document that either The root object mapping allows to index a JSON document that only contains its
starts with the actual mapping type, or only contains its fields. For fields. For example, the following `tweet` JSON can be indexed without
example, the following `tweet` JSON can be indexed: specifying the `tweet` type in the document itself:
[source,js] [source,js]
-------------------------------------------------- --------------------------------------------------
@ -19,20 +16,6 @@ example, the following `tweet` JSON can be indexed:
} }
-------------------------------------------------- --------------------------------------------------
But, also the following JSON can be indexed:
[source,js]
--------------------------------------------------
{
"tweet" : {
"message" : "This is a tweet!"
}
}
--------------------------------------------------
Out of the two, it is preferable to use the document *without* the type
explicitly set.
[float] [float]
==== Index / Search Analyzers ==== Index / Search Analyzers