﻿---
title: ignore_malformed
description: Sometimes you don’t have much control over the data that you receive. One user may send a login field that is a date, and another sends a login field...
url: https://www.elastic.co/elastic/docs-builder/docs/2948/reference/elasticsearch/mapping-reference/ignore-malformed
products:
  - Elasticsearch
applies_to:
  - Elastic Cloud Serverless: Generally available
  - Elastic Stack: Generally available
---

# ignore_malformed
Sometimes you don’t have much control over the data that you receive. One user may send a `login` field that is a [`date`](https://www.elastic.co/elastic/docs-builder/docs/2948/reference/elasticsearch/mapping-reference/date), and another sends a `login` field that is an email address.
Trying to index the wrong data type into a field throws an exception by default, and rejects the whole document. The `ignore_malformed` parameter, if set to `true`, allows the exception to be ignored. The malformed field is not indexed, but other fields in the document are processed normally.
For example:
```json

{
  "mappings": {
    "properties": {
      "number_one": {
        "type": "integer",
        "ignore_malformed": true
      },
      "number_two": {
        "type": "integer"
      }
    }
  }
}


{
  "text":       "Some text value",
  "number_one": "foo" <1>
}


{
  "text":       "Some text value",
  "number_two": "foo" <2>
}
```

The `ignore_malformed` setting is currently supported by the following [mapping types](https://www.elastic.co/elastic/docs-builder/docs/2948/reference/elasticsearch/mapping-reference/field-data-types):
<definitions>
  <definition term="Numeric">
    `long`, `integer`, `short`, `byte`, `double`, `float`, `half_float`, `scaled_float`
  </definition>
  <definition term="Boolean">
    `boolean`
  </definition>
  <definition term="Date">
    `date`
  </definition>
  <definition term="Date nanoseconds">
    `date_nanos`
  </definition>
  <definition term="Geopoint">
    `geo_point` for lat/lon points, although there is a [special case](#_ignore_malformed_geo_point) for out-of-range values
  </definition>
  <definition term="Geoshape">
    `geo_shape` for complex shapes like polygons
  </definition>
  <definition term="IP">
    `ip` for IPv4 and IPv6 addresses
  </definition>
</definitions>

<tip>
  The `ignore_malformed` setting value can be updated on existing fields using the [update mapping API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-put-mapping).
</tip>


## Index-level default

The `index.mapping.ignore_malformed` setting can be set on the index level to ignore malformed content globally across all allowed mapping types. Mapping types that don’t support the setting will ignore it if set on the index level.
```json

{
  "settings": {
    "index.mapping.ignore_malformed": true <1>
  },
  "mappings": {
    "properties": {
      "number_one": { <1>
        "type": "byte"
      },
      "number_two": {
        "type": "integer",
        "ignore_malformed": false <2>
      }
    }
  }
}
```


## Dealing with malformed fields

Malformed fields are silently ignored at indexing time when `ignore_malformed` is turned on.
Whenever possible it is recommended to keep the number of documents that have a malformed field contained,
or queries on this field will become meaningless.
Elasticsearch makes it easy to check how many documents have malformed fields by using `exists`,
`term` or `terms` queries on the special [`_ignored`](https://www.elastic.co/elastic/docs-builder/docs/2948/reference/elasticsearch/mapping-reference/mapping-ignored-field) field.

## The special case of `geo_point` fields

With [`geo_point`](https://www.elastic.co/elastic/docs-builder/docs/2948/reference/elasticsearch/mapping-reference/geo-point) fields,
there is the special case of values that have a syntactically valid format,
but the numerical values for `latitude` and `longitude` are out of range.
If `ignore_malformed` is `false`, an exception will be thrown as usual. But if it is `true`,
the document will be indexed correctly, by normalizing the latitude and longitude values into the valid range.
The special [`_ignored`](https://www.elastic.co/elastic/docs-builder/docs/2948/reference/elasticsearch/mapping-reference/mapping-ignored-field) field will not be set.
The original source document will remain as before, but indexed values, doc-values and stored fields will all be normalized.

## Limits for JSON Objects

You can’t use `ignore_malformed` with the following data types:
- [Nested data type](https://www.elastic.co/elastic/docs-builder/docs/2948/reference/elasticsearch/mapping-reference/nested)
- [Object data type](https://www.elastic.co/elastic/docs-builder/docs/2948/reference/elasticsearch/mapping-reference/object)
- [Range data types](https://www.elastic.co/elastic/docs-builder/docs/2948/reference/elasticsearch/mapping-reference/range)

You also can’t use `ignore_malformed` to ignore JSON objects submitted to fields of the wrong data type. A JSON object is any data surrounded by curly brackets `"{}"` and includes data mapped to the nested, object, and range data types.
If you submit a JSON object to an unsupported field, Elasticsearch will return an error and reject the entire document regardless of the `ignore_malformed` setting.