Bug on ignore_malformed in 5.4.3 version

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.

This bug is in your roadmap?

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