# org.elasticsearch.index.mapper.MapperParsingException: failed to parse \[target.gb\_size\] **URL:** \ **Category:** Elasticsearch\ **Created:** [April 24, 2018, 12:21am UTC](https://discuss.elastic.co/t/org-elasticsearch-index-mapper-mapperparsingexception-failed-to-parse-target-gb-size/129196 "2018-04-24T00:21:50Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![agonzalez](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@agonzalez](https://discuss.elastic.co/u/agonzalez)\ **Post date:** [April 24, 2018, 12:21am UTC](https://discuss.elastic.co/t/org-elasticsearch-index-mapper-mapperparsingexception-failed-to-parse-target-gb-size/129196/1 "2018-04-24T00:21:50Z")
I have a new instance using 6.2 and i am duplicating same PUT/POST requests to both 5.x and 6.2 In 6.2 i get this error because gb\_size is usually a float value but some times it is a N/A org.elasticsearch.index.mapper.MapperParsingException: failed to parse [target.gb\_size] In 5.X i get it indexed and see indexed docs with values of: N/A, 32569.08, 0, 1024, etc I have some docs in different indexes where some fields sometimes is an integer and other is empty or null or N/A. Is there any global property so this field always get indexed? I set ignore\_malformed to true to ignore fields that doesnt match the mapping but looks like doesnt work in 6x? put /\_template/all { "order": 0, "index\_patterns": "ueb-\*", "settings": { "index": { "mapping": { "ignore\_malformed": "true" } } } } ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 22, 2018, 12:21am UTC](https://discuss.elastic.co/t/org-elasticsearch-index-mapper-mapperparsingexception-failed-to-parse-target-gb-size/129196/2 "2018-05-22T00:21:51Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.