Put Mappingedit
The PUT mapping API allows you to add fields to an existing index or to change search only settings of existing fields.
Creates an index called | |
Uses the PUT mapping API to add a new field called |
More information on how to define type mappings can be found in the mapping section.
Multi-indexedit
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:
# Create the two indices PUT twitter-1 PUT twitter-2 # Update both mappings PUT /twitter-1,twitter-2/_mapping/_doc{ "properties": { "user_name": { "type": "text" } } }
Note that the indices specified ( |
When updating the _default_ mapping with the
PUT mapping API, the new mapping is not merged with
the existing mapping. Instead, the new _default_ mapping replaces the
existing one.
Updating field mappingsedit
In general, the mapping for existing fields cannot be updated. There are some exceptions to this rule. For instance:
-
new
propertiescan be added to Object datatype fields. - new multi-fields can be added to existing fields.
-
the
ignore_aboveparameter can be updated.
For example:
PUT my_index{ "mappings": { "_doc": { "properties": { "name": { "properties": { "first": { "type": "text" } } }, "user_id": { "type": "keyword" } } } } } PUT my_index/_mapping/_doc { "properties": { "name": { "properties": { "last": {
"type": "text" } } }, "user_id": { "type": "keyword", "ignore_above": 100
} } }
Create an index with a | |
Add a | |
Update the |
Each mapping parameter specifies whether or not its setting can be updated on an existing field.