# ES Cloud: How to fix \[include\_in\_all\] is not allowed for indices created on or after version 6.0.0

**URL:** <https://discuss.elastic.co/t/es-cloud-how-to-fix-include-in-all-is-not-allowed-for-indices-created-on-or-after-version-6-0-0/107806>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [November 15, 2017, 7:01pm UTC](https://discuss.elastic.co/t/es-cloud-how-to-fix-include-in-all-is-not-allowed-for-indices-created-on-or-after-version-6-0-0/107806 "2017-11-15T19:01:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![suchitgupta](https://avatars.discourse-cdn.com/v4/letter/s/d9b06d/32.png) [@suchitgupta](https://discuss.elastic.co/u/suchitgupta)\
**Post date:** [November 15, 2017, 7:01pm UTC](https://discuss.elastic.co/t/es-cloud-how-to-fix-include-in-all-is-not-allowed-for-indices-created-on-or-after-version-6-0-0/107806/1 "2017-11-15T19:01:42Z")

</div>

Hi Team,

Yesterday we upgraded to ES Cloud 6.0.0. We are using docker image of Logstash 5.6.3 for pushing the logs to ES Cloud.

The upgrade is not going well for us as we are getting following exceptions in our logstash:

> "reason"=\>"Failed to parse mapping [_default_]: [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.", "caused\_by"=\>{"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."}}}}}

Is there a way, I can update my logstash.conf and fix this issue? or is any configuration in ES cloud that I can help me.

---

<div class="post-metadata">

**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\
**Post date:** [November 16, 2017, 10:26pm UTC](https://discuss.elastic.co/t/es-cloud-how-to-fix-include-in-all-is-not-allowed-for-indices-created-on-or-after-version-6-0-0/107806/2 "2017-11-16T22:26:54Z")

</div>

Hi @suchitgupta

Please raise this via support: [https://discuss.elastic.co/t/now-live-new-elastic-cloud-standard-support/84161](https://discuss.elastic.co/t/now-live-new-elastic-cloud-standard-support/84161).  
This channel is dedicated to Elastic Cloud Enterprise, which is a different product.

(This looks like an Elasticsearch issue not in anyway EC specific, so you might get fastest/best responses by reposting this in the Elasticsearch Discuss forum?)

Thanks  
Alex

---

<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:** [November 30, 2017, 10:27pm UTC](https://discuss.elastic.co/t/es-cloud-how-to-fix-include-in-all-is-not-allowed-for-indices-created-on-or-after-version-6-0-0/107806/3 "2017-11-30T22:27:08Z")

</div>

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