123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112 |
- [[indices-put-mapping]]
- == Put Mapping
- The PUT mapping API allows you to add fields to an existing index or to change search only settings of existing fields.
- [source,js]
- --------------------------------------------------
- PUT twitter <1>
- {}
- PUT twitter/_mapping <2>
- {
- "properties": {
- "email": {
- "type": "keyword"
- }
- }
- }
- --------------------------------------------------
- // CONSOLE
- <1> <<indices-create-index,Creates an index>> called `twitter` without any mapping.
- <2> Uses the PUT mapping API to add a new field called `email`.
- More information on how to define mappings can be found in the <<mapping,mapping>> section.
- NOTE: Before 7.0.0, the 'mappings' definition used to include a type name. Although specifying
- types in requests is now deprecated, a type can still be provided if the request parameter
- include_type_name is set. For more details, please see <<removal-of-types>>.
- [float]
- === Multi-index
- The PUT mapping API can be applied to multiple indices with a single request.
- For example, we can update the `twitter-1` and `twitter-2` mappings at the same time:
- [source,js]
- --------------------------------------------------
- # Create the two indices
- PUT twitter-1
- PUT twitter-2
- # Update both mappings
- PUT /twitter-1,twitter-2/_mapping <1>
- {
- "properties": {
- "user_name": {
- "type": "text"
- }
- }
- }
- --------------------------------------------------
- // CONSOLE
- <1> Note that the indices specified (`twitter-1,twitter-2`) follows <<multi-index,multiple index names>> and wildcard format.
- [[updating-field-mappings]]
- [float]
- === Updating field mappings
- In general, the mapping for existing fields cannot be updated. There are some
- exceptions to this rule. For instance:
- * new <<properties>> can be added to <<object>> fields.
- * new <<multi-fields,multi-fields>> can be added to existing fields.
- * the <<ignore-above>> parameter can be updated.
- For example:
- [source,js]
- -----------------------------------
- PUT my_index <1>
- {
- "mappings": {
- "properties": {
- "name": {
- "properties": {
- "first": {
- "type": "text"
- }
- }
- },
- "user_id": {
- "type": "keyword"
- }
- }
- }
- }
- PUT my_index/_mapping
- {
- "properties": {
- "name": {
- "properties": {
- "last": { <2>
- "type": "text"
- }
- }
- },
- "user_id": {
- "type": "keyword",
- "ignore_above": 100 <3>
- }
- }
- }
- -----------------------------------
- // CONSOLE
- <1> Create an index with a `first` field under the `name` <<object>> field, and a `user_id` field.
- <2> Add a `last` field under the `name` object field.
- <3> Update the `ignore_above` setting from its default of 0.
- Each <<mapping-params,mapping parameter>> specifies whether or not its setting
- can be updated on an existing field.
|