# Ignore\_malformed not operating in field?
**URL:** https://discuss.elastic.co/t/ignore-malformed-not-operating-in-field/79693
**Category:** Elasticsearch
**Created:** [March 23, 2017, 6:54am UTC](https://discuss.elastic.co/t/ignore-malformed-not-operating-in-field/79693 "2017-03-23T06:54:59Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@ChronosWS](https://discuss.elastic.co/u/ChronosWS)
#### Post date: [March 23, 2017, 6:54am UTC](https://discuss.elastic.co/t/ignore-malformed-not-operating-in-field/79693/1 "2017-03-23T06:54:59Z")
Example mapping for a variable-type metric value:
"value": {
"ignore\_above": 1024,
"type": "keyword",
"fields": {
"integer": {
"type": "integer",
"ignore\_malformed": true
},
"float": {
"type": "float",
"ignore\_malformed": true
}
}
}
Attempting to put this via logstash yields:
06:35:35.711 [[main]\>worker0] WARN logstash.outputs.elasticsearch - Failed action. {:status=\>400, :action=\>["index", {:\_id=\>nil, :\_index=\>"metric-2017.03.23", :\_type=\>"metric", :\_routing=\>nil}, 2017-03-23T03:58:51.291Z %{host} %{message}], :response=\>{"index"=\>{"\_index"=\>"metric-2017.03.23", "\_type"=\>"metric", "\_id"=\>"AVr54Lp5MxsbdHINq-RJ", "status"=\>400, "error"=\>{"type"=\>"mapper\_parsing\_exception", "reason"=\>"failed to parse [value.integer]", "caused\_by"=\>{"type"=\>"json\_parse\_exception", "reason"=\>"Numeric value (37211860992) out of range of int\n at [Source: org.elasticsearch.common.bytes.BytesReference$MarkSupportingStreamInputWrapper@78c7e3aa; line: 1, column: 394]"}}}}}
It is my understanding that mapper\_parsing\_exceptions should NOT block documents from being indexed if ignore\_malformed is applied. Is this not true?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 20, 2017, 6:55am UTC](https://discuss.elastic.co/t/ignore-malformed-not-operating-in-field/79693/2 "2017-04-20T06:55:08Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.