# Failed to parse mapping for index

**URL:** <https://discuss.elastic.co/t/failed-to-parse-mapping-for-index/110102>\
**Category:** Kibana\
**Created:** [December 4, 2017, 8:38am UTC](https://discuss.elastic.co/t/failed-to-parse-mapping-for-index/110102 "2017-12-04T08:38:07Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jasonespo](https://avatars.discourse-cdn.com/v4/letter/j/898d66/32.png) [@Jasonespo](https://discuss.elastic.co/u/Jasonespo)\
**Post date:** [December 4, 2017, 8:38am UTC](https://discuss.elastic.co/t/failed-to-parse-mapping-for-index/110102/1 "2017-12-04T08:38:08Z")

</div>

I have just updated my stack to 6.0.0 and I am getting the following error:

017-12-01 10:47:45.653 INFO 3211 --- [/O dispatcher 2] p.c.ElasticSearchRestClientConfiguration : Error for compass/null for INDEX operation: ElasticsearchException[Elasticsearch exception [type=mapper\_parsing\_exception, reason=Failed to parse mapping [compass]: [include\_in\_all] is not allowed for indices created on or after version 6.0.0 as [\_all] is deprecated. As a replacement, you can use an [copy\_to] on mapping fields to create your own catch all field.]]; nested: ElasticsearchException[Elasticsearch exception [type=mapper\_parsing\_exception, reason=[include\_in\_all] is not allowed for indices created on or after version 6.0.0 as [\_all] is deprecated. As a replacement, you can use an [copy\_to] on mapping fields to create your own catch all field.]];

I have set my cluster in elastic cloud to create a new index automatically, and it was not able to create an index on the 1st of December due to the mappings being deprecated.

Is there a way to create a new mapping for the cluster to automatically conform to and create new indexes each month from the newly defined mapping?

Jason

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [December 4, 2017, 8:40am UTC](https://discuss.elastic.co/t/failed-to-parse-mapping-for-index/110102/2 "2017-12-04T08:40:21Z")

</div>

It seems like you have an old index template that uses `include_in_all`, which is no longer supported.

---

<div class="post-metadata">

**Author:** ![Jasonespo](https://avatars.discourse-cdn.com/v4/letter/j/898d66/32.png) [@Jasonespo](https://discuss.elastic.co/u/Jasonespo)\
**Post date:** [December 4, 2017, 8:44am UTC](https://discuss.elastic.co/t/failed-to-parse-mapping-for-index/110102/3 "2017-12-04T08:44:38Z")

</div>

How do I edit my index template?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [December 4, 2017, 8:49am UTC](https://discuss.elastic.co/t/failed-to-parse-mapping-for-index/110102/4 "2017-12-04T08:49:18Z")

</div>

Get the current one using the [index template API](https://www.elastic.co/guide/en/elasticsearch/reference/6.0/indices-templates.html) and update it. You can the push it back into the cluster using the same API. If you are using the default Logstash template, you can just upload the [standard 6.0 template](https://github.com/logstash-plugins/logstash-output-elasticsearch/blob/master/lib/logstash/outputs/elasticsearch/elasticsearch-template-es6x.json) and overwrite the existing one.

---

<div class="post-metadata">

**Author:** ![Jasonespo](https://avatars.discourse-cdn.com/v4/letter/j/898d66/32.png) [@Jasonespo](https://discuss.elastic.co/u/Jasonespo)\
**Post date:** [December 4, 2017, 10:08am UTC](https://discuss.elastic.co/t/failed-to-parse-mapping-for-index/110102/5 "2017-12-04T10:08:23Z")

</div>

Is there a default index pattern that my cluster will use? When I use a "GET /\_template/" I have several index patterns that appear, including logstash-_, security-_, tid-\* etc

Will I need to edit each to remove the deprecated lines?

---

<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:** [January 1, 2018, 10:08am UTC](https://discuss.elastic.co/t/failed-to-parse-mapping-for-index/110102/6 "2018-01-01T10:08:37Z")

</div>

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