diff --git a/docs/reference/indices/put-mapping.asciidoc b/docs/reference/indices/put-mapping.asciidoc index 0ea7fdadcbe39..d7082f2db1125 100644 --- a/docs/reference/indices/put-mapping.asciidoc +++ b/docs/reference/indices/put-mapping.asciidoc @@ -74,7 +74,7 @@ Defaults to `false`. fields, this mapping can include: * Field name -* <> +* <> * <> For existing fields, see <>. diff --git a/docs/reference/mapping.asciidoc b/docs/reference/mapping.asciidoc index eef4a96390283..e146b1194f6a4 100644 --- a/docs/reference/mapping.asciidoc +++ b/docs/reference/mapping.asciidoc @@ -22,38 +22,14 @@ treated. Examples of metadata fields include the document's <>, <>, and <> fields. -<> or _properties_:: +<>:: A mapping contains a list of fields or `properties` pertinent to the -document. +document. Each field has its own <>. NOTE: Before 7.0.0, the 'mappings' definition used to include a type name. For more details, please see <>. -[discrete] -[[field-datatypes]] -== Field data types - -Each field has a data `type` which can be: - -* a simple type like <>, <>, <>, <>, - <>, <> or <>. -* a type which supports the hierarchical nature of JSON such as - <> or <>. -* or a specialised type like <>, - <>, or <>. - -It is often useful to index the same field in different ways for different -purposes. For instance, a `string` field could be <> as -a `text` field for full-text search, and as a `keyword` field for -sorting or aggregations. Alternatively, you could index a string field with -the <>, the -<> analyzer, and the -<>. - -This is the purpose of _multi-fields_. Most data types support multi-fields -via the <> parameter. - [[mapping-limit-settings]] [discrete] === Settings to prevent mappings explosion