# \_all and include\_in\_all mapping in ElasticSearch 6.0

**URL:** <https://discuss.elastic.co/t/-all-and-include-in-all-mapping-in-elasticsearch-6-0/80431>\
**Category:** Elasticsearch\
**Created:** [March 29, 2017, 7:56am UTC](https://discuss.elastic.co/t/-all-and-include-in-all-mapping-in-elasticsearch-6-0/80431 "2017-03-29T07:56:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ptrussart](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ptrussart/32/25648_2.png) [@ptrussart](https://discuss.elastic.co/u/ptrussart)\
**Post date:** [March 29, 2017, 7:56am UTC](https://discuss.elastic.co/t/-all-and-include-in-all-mapping-in-elasticsearch-6-0/80431/1 "2017-03-29T07:56:34Z")

</div>

Hello,

I have seen here [https://github.com/elastic/elasticsearch/issues/22923](https://github.com/elastic/elasticsearch/issues/22923) that the `include_in_all` parameter will no longer be available in ES 6.0 as the `_all` field will also stop to be created.  
I use it a lot in my app because on one hand, I don't want some "technical" hidden fields that I don't want to be indexed when a user search for a value (using `match_all`) but on the other hand, I do want to be able to perform a query on this field.

What will be configurable in the mapping to solve this problem ?

Regards,  
Pierre.

---

<div class="post-metadata">

**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\
**Post date:** [March 29, 2017, 8:10am UTC](https://discuss.elastic.co/t/-all-and-include-in-all-mapping-in-elasticsearch-6-0/80431/2 "2017-03-29T08:10:58Z")

</div>

You will still be able to use `copy_to`, potentially with dynamic templates in order ot add it to most fields automatically.

---

<div class="post-metadata">

**Author:** ![ptrussart](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ptrussart/32/25648_2.png) [@ptrussart](https://discuss.elastic.co/u/ptrussart)\
**Post date:** [April 3, 2017, 10:25am UTC](https://discuss.elastic.co/t/-all-and-include-in-all-mapping-in-elasticsearch-6-0/80431/3 "2017-04-03T10:25:47Z")

</div>

Thanks for your answer.

I have a related question : as far as I understand (based on what I've read here [https://www.elastic.co/guide/en/elasticsearch/reference/5.3/copy-to.html](https://www.elastic.co/guide/en/elasticsearch/reference/5.3/copy-to.html) ), when you use `copy_to`, it is the field value which is copied, not the terms (which result from the analysis process).

Currently I have defined some fields with a custom analyzer.  
Using the standard `_all` field, it seems to me that the analyzed terms were stored in as I was able to search on analyzed terms.

Now iIf I want to have the same behavior with a custom `_all` field, should I apply the custom analyser on my custom `_all` field too ?

---

<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:** [May 1, 2017, 10:26am UTC](https://discuss.elastic.co/t/-all-and-include-in-all-mapping-in-elasticsearch-6-0/80431/4 "2017-05-01T10:26:07Z")

</div>

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