# Bug on ignore\_malformed in 5.4.3 version

**URL:** <https://discuss.elastic.co/t/bug-on-ignore-malformed-in-5-4-3-version/100107>\
**Category:** Elasticsearch\
**Created:** [September 11, 2017, 5:32pm UTC](https://discuss.elastic.co/t/bug-on-ignore-malformed-in-5-4-3-version/100107 "2017-09-11T17:32:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mvleandro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mvleandro/32/14268_2.png) [@mvleandro](https://discuss.elastic.co/u/mvleandro)\
**Post date:** [September 11, 2017, 5:32pm UTC](https://discuss.elastic.co/t/bug-on-ignore-malformed-in-5-4-3-version/100107/1 "2017-09-11T17:32:56Z")

</div>

Hello everyone!

The Elasticsearch's documentation say you can use the flag ignore\_malformed on mappings to index documents with some fields malformeds, ignoring this malformed fields and saving the others.

The reality is different. I configured my index mapping to expect an string and when a try to send an integer, for example, the Elasticsearch ignore this malformed field and index the document, but when i send an object instead, i still receiving an exception from Elasticsearch Api and a lost the data.

I saw an old thread on github relating the bug with ignore\_malformed but this thread still open and with no expectation to solve.

> <https://github.com/elastic/elasticsearch/issues/12366>

This bug is in your roadmap?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 9, 2017, 5:33pm UTC](https://discuss.elastic.co/t/bug-on-ignore-malformed-in-5-4-3-version/100107/2 "2017-10-09T17:33:03Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.