_all and include_in_all mapping in ElasticSearch 6.0

[ptrussart]

Hello,

I have seen here 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.

[jpountz (Adrien Grand)]

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

[ptrussart]

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 ), 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 ?