Update field mappings

POST also PUT /{index}/_mapping

Api key auth

Add new fields to an existing data stream or index. You can use the update mapping API to:

Add a new field to an existing index
Update mappings for multiple indices in a single request
Add new properties to an object field
Enable multi-fields for an existing field
Update supported mapping parameters
Change a field's mapping using reindexing
Rename a field using a field alias

Learn how to use the update mapping API with practical examples in the Update mapping API examples guide.

Required authorization

Index privileges: manage

More about mapping parameters

Path Parameters

index union IndexName | [] IndexName required: A comma-separated list of index names the mapping should be added to (supports wildcards). Use _all or omit to add the mapping on all indices.

Query Parameters

allow_no_indices boolean · default: true

A setting that does two separate checks on the index expression. If false, the request returns an error (1) if any wildcard expression (including _all and *) resolves to zero matching indices or (2) if the complete set of resolved indices, aliases or data streams is empty after all expressions are evaluated. If true, index expressions that resolve to no indices are allowed and the request returns an empty result.

expand_wildcards string ExpandWildcards · default: open

Type of index that wildcard patterns can match. If the request can target data streams, this argument determines whether wildcard expressions match hidden data streams. Supports comma-separated values, such as open,hidden.

Supported values include:

all: Match any data stream or index, including hidden ones.
open: Match open, non-hidden indices. Also matches any non-hidden data stream.
closed: Match closed, non-hidden indices. Also matches any non-hidden data stream. Data streams cannot be closed.
hidden: Match hidden data streams and hidden indices. Must be combined with open, closed, or both.
none: Wildcard expressions are not accepted.

Values: all open closed hidden none

ignore_unavailable boolean · default: false

If false, the request returns an error if it targets a concrete (non-wildcarded) index, alias, or data stream that is missing, closed, or otherwise unavailable. If true, unavailable concrete targets are silently ignored.

master_timeout string Duration · default: 30s

Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error.

timeout string Duration · default: 30s

Period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error.

write_index_only boolean · default: false

If true, the mappings are applied only to the current write index for the target.

Request

date_detection boolean: Controls whether dynamic date detection is enabled.
dynamic enum DynamicMapping: Controls whether new fields are added dynamically.; Values: strict runtime true false
dynamic_date_formats [] string: If date detection is enabled then new string fields are checked against 'dynamic_date_formats' and if the value matches then a new date field is added instead of string.
dynamic_templates [] string to DynamicTemplate: Specify dynamic templates for the mapping.
_field_names {} FieldNamesField: Control whether field names are enabled for the index.
_meta Metadata: A mapping type can have custom meta data associated with it. These are not used at all by Elasticsearch, but can be used to store application-specific metadata.
numeric_detection boolean · default: false: Automatically map strings into numeric data types for all fields.
properties map string to Property: Mapping for a field. For new fields, this mapping can include:

Field name

Field data type

Mapping parameters
_routing {} RoutingField: Enable making a routing value required on indexed documents.
_source {} SourceField: Control whether the _source field is enabled on the index.
runtime RuntimeFields: Mapping of runtime fields for the index.

Response

application/json

Examples

The update mapping API can be applied to multiple data streams or indices with a single request. For example, run PUT /my-index-000001,my-index-000002/_mapping to update mappings for the my-index-000001 and my-index-000002 indices at the same time.

Request Console 1 / 8 languages

Console Kibana Dev Tools

POST /my-index-000001/_mapping
{
  "properties": {
    "user": {
      "properties": {
        "name": {
          "type": "keyword"
        }
      }
    }
  }
}

JavaScript Elasticsearch JavaScript Client

const response = await client.indices.putMapping({
  index: "my-index-000001",
  properties: {
    user: {
      properties: {
        name: {
          type: "keyword",
        },
      },
    },
  },
});

Python Elasticsearch Python Client

resp = client.indices.put_mapping(
    index="my-index-000001",
    properties={
        "user": {
            "properties": {
                "name": {
                    "type": "keyword"
                }
            }
        }
    },
)

curl Shell

curl -X POST "$ELASTICSEARCH_URL/my-index-000001/_mapping" \
  -H "Authorization: ApiKey $ELASTIC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "properties": {
      "user": {
        "properties": {
          "name": {
            "type": "keyword"
          }
        }
      }
    }
  }'

Java Elasticsearch Java Client

client.indices().putMapping(p -> p
    .index("my-index-000001")
    .properties("user", pr -> pr
        .object(o -> o
            .properties("name", pro -> pro
                .keyword(k -> k)
            )
        )
    )
);

C# Elasticsearch .NET Client

var response = await client.Indices
    .PutMappingAsync(indices: new[] { "my-index-000001" }, d1 => d1
        .Properties(d2 => d2
            .Object(x => x.User, d3 => d3
                .Properties(d4 => d4
                    .Keyword(x => x.Name)
                )
            )
        )
    );

PHP Elasticsearch PHP Client

$resp = $client->indices()->putMapping([
    "index" => "my-index-000001",
    "body" => [
        "properties" => [
            "user" => [
                "properties" => [
                    "name" => [
                        "type" => "keyword",
                    ],
                ],
            ],
        ],
    ],
]);

Ruby Elasticsearch Ruby Client

response = client.indices.put_mapping(
  index: "my-index-000001",
  body: {
    "properties": {
      "user": {
        "properties": {
          "name": {
            "type": "keyword"
          }
        }
      }
    }
  }
)

Response

No example

Required authorization

Path Parameters

Query Parameters { allow_no_indices , expand_wildcards , ignore_unavailable , master_timeout , timeout , write_index_only , }

Request { date_detection , dynamic , dynamic_date_formats , dynamic_templates , _field_names , _meta , numeric_detection , properties , _routing , _source , runtime , }

Response

Query Parameters

Request