# Ignore malformed **URL:** \ **Category:** Elasticsearch\ **Tags:** es-hadoop\ **Created:** [July 28, 2016, 8:54pm UTC](https://discuss.elastic.co/t/ignore-malformed/56674 "2016-07-28T20:54:50Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Roy\_Russo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roy_russo/32/44835_2.png) [@Roy\_Russo](https://discuss.elastic.co/u/Roy_Russo)\ **Post date:** [July 28, 2016, 8:54pm UTC](https://discuss.elastic.co/t/ignore-malformed/56674/1 "2016-07-28T20:54:51Z")
We are looking to upgrade to 2.x and then 5.x. In the past, we had to fork the ES-Hadoop library to swallow numberformatexceptions on read, when it tries to cast a string to an int (as per the ES mapping). This is also mentioned here: [https://github.com/elastic/elasticsearch-hadoop/issues/663](https://github.com/elastic/elasticsearch-hadoop/issues/663) We are curious if this is still an issue with the ES-Hadoop library, or if a flag has been added to observe the ignore\_malformed flag in ES. We can't guarantee perfect customer data, so that flag is turned on in most of our indices. In the past, ES-Hadoop would blow up the whole job on just one improper cast. Is there a workaround? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:23pm UTC](https://discuss.elastic.co/t/ignore-malformed/56674/2 "2017-07-06T13:23:47Z")