# Elasticsearch 6 and the disappearing \_all field

**URL:** <https://discuss.elastic.co/t/elasticsearch-6-and-the-disappearing--all-field/85871>\
**Category:** Elasticsearch\
**Created:** [May 16, 2017, 7:47am UTC](https://discuss.elastic.co/t/elasticsearch-6-and-the-disappearing--all-field/85871 "2017-05-16T07:47:20Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![dakrone](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dakrone/32/23351_2.png) [@dakrone](https://discuss.elastic.co/u/dakrone)\
**Post date:** [May 16, 2017, 4:18pm UTC](https://discuss.elastic.co/t/elasticsearch-6-and-the-disappearing--all-field/85871/6 "2017-05-16T16:18:52Z")

</div>

> [@Roeland](#):
>
> If these queries are searching over all the fields, how do they cope with the different analyzers that I use in those fields. What about multi-fields?

The queries will use the per-field analyzer when they analyze, so assume you have a string multifield with a non-analyzed and analyzed version, the `all_fields` query will generate two queries, one that is non-analyzed and one that is analyzed.

I also gave a talk covering this at Elasticon 2017, you can watch the video here - [https://www.elastic.co/elasticon/conf/2017/sf/elasticsearch-search-improvements](https://www.elastic.co/elasticon/conf/2017/sf/elasticsearch-search-improvements)

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-6-and-the-disappearing--all-field/85871)._