# ES 1.2.0 MapperParsingException when create default mapping with 'include\_in\_all' nested

**URL:** <https://discuss.elastic.co/t/es-1-2-0-mapperparsingexception-when-create-default-mapping-with-include-in-all-nested/17702>\
**Category:** Elasticsearch\
**Created:** [May 24, 2014, 12:55am UTC](https://discuss.elastic.co/t/es-1-2-0-mapperparsingexception-when-create-default-mapping-with-include-in-all-nested/17702 "2014-05-24T00:55:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jeffz](https://avatars.discourse-cdn.com/v4/letter/j/e9c0ed/32.png) [@Jeffz](https://discuss.elastic.co/u/Jeffz)\
**Post date:** [May 24, 2014, 12:55am UTC](https://discuss.elastic.co/t/es-1-2-0-mapperparsingexception-when-create-default-mapping-with-include-in-all-nested/17702/1 "2014-05-24T00:55:36Z")

</div>

One noticeable issue found with ES 1.2 during our deployment is that it threw exception when created default mappings with ‘include\_in\_all’ nested under it (doesn’t matter it’s set to true/false). For example, the following index creation command returns error when against ES 1.2 but it works well against ES 1.1.

PUT test  
{  
"mappings": {  
"_default_": {  
"include\_in\_all": true  
}  
}  
}

Result  
{  
"error": "MapperParsingException[mapping [_default_]]; nested: MapperParsingException[Root type mapping not empty after parsing! Remaining fields: [include\_in\_all : true]]; ",  
"status": 400  
}

Is this a regression with ES 1.2?

---

<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:** [July 6, 2017, 1:27am UTC](https://discuss.elastic.co/t/es-1-2-0-mapperparsingexception-when-create-default-mapping-with-include-in-all-nested/17702/2 "2017-07-06T01:27:15Z")

</div>