# \_all like multifield field can be defined like \_all in mappings?

**URL:** <https://discuss.elastic.co/t/-all-like-multifield-field-can-be-defined-like--all-in-mappings/14277>\
**Category:** Elasticsearch\
**Created:** [November 6, 2013, 12:10am UTC](https://discuss.elastic.co/t/-all-like-multifield-field-can-be-defined-like--all-in-mappings/14277 "2013-11-06T00:10:25Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![roytmana](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roytmana/32/44855_2.png) [@roytmana](https://discuss.elastic.co/u/roytmana)\
**Post date:** [November 6, 2013, 12:10am UTC](https://discuss.elastic.co/t/-all-like-multifield-field-can-be-defined-like--all-in-mappings/14277/1 "2013-11-06T00:10:25Z")

</div>

Hello,

I am using several \_all like multifields to collect searchable data from  
dozens of properties  
some of my \_all like fields hold original terms other stemmed or shingled

I am wondering how ES identify default search analyzer if not specified in  
query? Can my all fields have mapping definitions like \_all has?

I suspect not since I can use different analysis feeding into those fields  
from different properties.

Does it mean that while using these fields I must specify search analyzer  
in all my queries?

Thank you,  
Alex

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 6, 2013, 3:07am UTC](https://discuss.elastic.co/t/-all-like-multifield-field-can-be-defined-like--all-in-mappings/14277/2 "2013-11-06T03:07:03Z")

</div>

Let's say that your \_all like field is myall.

When you define a multifield, it creates "subfields" like:

myall.myall (default field used when you search in myall)  
myall.multi1  
myall.multi2

Each of these could have its own analyzer (index analyzer and search analyzer).

So when you search in myall, the myall.myall analyzer will be applied to your search query. If you search in myall.multi1, then myall.multi1 analyzer will be applied as well for this query.

Makes sense?

--  
David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 6 nov. 2013 à 01:10, AlexR [roytmana@gmail.com](mailto:roytmana@gmail.com) a écrit :

Hello,

I am using several \_all like multifields to collect searchable data from dozens of properties  
some of my \_all like fields hold original terms other stemmed or shingled

I am wondering how ES identify default search analyzer if not specified in query? Can my all fields have mapping definitions like \_all has?

I suspect not since I can use different analysis feeding into those fields from different properties.

Does it mean that while using these fields I must specify search analyzer in all my queries?

## Thank you, Alex

You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Amit\_Soni](https://avatars.discourse-cdn.com/v4/letter/a/c0e974/32.png) [@Amit\_Soni](https://discuss.elastic.co/u/Amit_Soni)\
**Post date:** [November 6, 2013, 6:30pm UTC](https://discuss.elastic.co/t/-all-like-multifield-field-can-be-defined-like--all-in-mappings/14277/3 "2013-11-06T18:30:58Z")

</div>

Alex - Would you mind sharing a snippet of how you have defined a new myAll  
field similar to "\_all". I need to do the same and hence looking for an  
example.

-Amit.

On Tue, Nov 5, 2013 at 7:07 PM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote:

> Let's say that your \_all like field is myall.
> 
> When you define a multifield, it creates "subfields" like:
> 
> myall.myall (default field used when you search in myall)  
> myall.multi1  
> myall.multi2
> 
> Each of these could have its own analyzer (index analyzer and search  
> analyzer).
> 
> So when you search in myall, the myall.myall analyzer will be applied to  
> your search query. If you search in myall.multi1, then myall.multi1  
> analyzer will be applied as well for this query.
> 
> Makes sense?
> 
> --  
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
> Le 6 nov. 2013 à 01:10, AlexR [roytmana@gmail.com](mailto:roytmana@gmail.com) a écrit :
> 
> Hello,
> 
> I am using several \_all like multifields to collect searchable data from  
> dozens of properties  
> some of my \_all like fields hold original terms other stemmed or shingled
> 
> I am wondering how ES identify default search analyzer if not specified in  
> query? Can my all fields have mapping definitions like \_all has?
> 
> I suspect not since I can use different analysis feeding into those fields  
> from different properties.
> 
> Does it mean that while using these fields I must specify search analyzer  
> in all my queries?
> 
> Thank you,  
> Alex
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![roytmana](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roytmana/32/44855_2.png) [@roytmana](https://discuss.elastic.co/u/roytmana)\
**Post date:** [November 6, 2013, 11:24pm UTC](https://discuss.elastic.co/t/-all-like-multifield-field-can-be-defined-like--all-in-mappings/14277/4 "2013-11-06T23:24:19Z")

</div>

see mapping for all field in [multifield-boost.json · GitHub](https://gist.github.com/roytmana/7330956)  
Alex - Would you mind sharing a snippet of how you have defined a new myAll  
field similar to "\_all". I need to do the same and hence looking for an  
example.

-Amit.

On Tue, Nov 5, 2013 at 7:07 PM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote:

> Let's say that your \_all like field is myall.
> 
> When you define a multifield, it creates "subfields" like:
> 
> myall.myall (default field used when you search in myall)  
> myall.multi1  
> myall.multi2
> 
> Each of these could have its own analyzer (index analyzer and search  
> analyzer).
> 
> So when you search in myall, the myall.myall analyzer will be applied to  
> your search query. If you search in myall.multi1, then myall.multi1  
> analyzer will be applied as well for this query.
> 
> Makes sense?
> 
> --  
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
> Le 6 nov. 2013 à 01:10, AlexR [roytmana@gmail.com](mailto:roytmana@gmail.com) a écrit :
> 
> Hello,
> 
> I am using several \_all like multifields to collect searchable data from  
> dozens of properties  
> some of my \_all like fields hold original terms other stemmed or shingled
> 
> I am wondering how ES identify default search analyzer if not specified in  
> query? Can my all fields have mapping definitions like \_all has?
> 
> I suspect not since I can use different analysis feeding into those fields  
> from different properties.
> 
> Does it mean that while using these fields I must specify search analyzer  
> in all my queries?
> 
> Thank you,  
> Alex
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to a topic in the  
Google Groups "elasticsearch" group.  
To unsubscribe from this topic, visit  
[https://groups.google.com/d/topic/elasticsearch/jNZPS57pyOI/unsubscribe](https://groups.google.com/d/topic/elasticsearch/jNZPS57pyOI/unsubscribe).  
To unsubscribe from this group and all its topics, send an email to  
[elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Amit\_Soni](https://avatars.discourse-cdn.com/v4/letter/a/c0e974/32.png) [@Amit\_Soni](https://discuss.elastic.co/u/Amit_Soni)\
**Post date:** [November 7, 2013, 6:15am UTC](https://discuss.elastic.co/t/-all-like-multifield-field-can-be-defined-like--all-in-mappings/14277/5 "2013-11-07T06:15:20Z")

</div>

Thanks a lot Alex!

-Amit.

On Wed, Nov 6, 2013 at 3:24 PM, Alex Roytman [roytmana@gmail.com](mailto:roytmana@gmail.com) wrote:

> see mapping for all field in [multifield-boost.json · GitHub](https://gist.github.com/roytmana/7330956)  
> Alex - Would you mind sharing a snippet of how you have defined a new  
> myAll field similar to "\_all". I need to do the same and hence looking for  
> an example.
> 
> -Amit.
> 
> On Tue, Nov 5, 2013 at 7:07 PM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote:
> 
> > Let's say that your \_all like field is myall.
> > 
> > When you define a multifield, it creates "subfields" like:
> > 
> > myall.myall (default field used when you search in myall)  
> > myall.multi1  
> > myall.multi2
> > 
> > Each of these could have its own analyzer (index analyzer and search  
> > analyzer).
> > 
> > So when you search in myall, the myall.myall analyzer will be applied to  
> > your search query. If you search in myall.multi1, then myall.multi1  
> > analyzer will be applied as well for this query.
> > 
> > Makes sense?
> > 
> > --  
> > David 😉  
> > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > 
> > Le 6 nov. 2013 à 01:10, AlexR [roytmana@gmail.com](mailto:roytmana@gmail.com) a écrit :
> > 
> > Hello,
> > 
> > I am using several \_all like multifields to collect searchable data from  
> > dozens of properties  
> > some of my \_all like fields hold original terms other stemmed or shingled
> > 
> > I am wondering how ES identify default search analyzer if not specified  
> > in query? Can my all fields have mapping definitions like \_all has?
> > 
> > I suspect not since I can use different analysis feeding into those  
> > fields from different properties.
> > 
> > Does it mean that while using these fields I must specify search analyzer  
> > in all my queries?
> > 
> > Thank you,  
> > Alex
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> You received this message because you are subscribed to a topic in the  
> Google Groups "elasticsearch" group.  
> To unsubscribe from this topic, visit  
> [https://groups.google.com/d/topic/elasticsearch/jNZPS57pyOI/unsubscribe](https://groups.google.com/d/topic/elasticsearch/jNZPS57pyOI/unsubscribe).  
> To unsubscribe from this group and all its topics, send an email to  
> [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> 
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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:** [July 6, 2017, 2:08am UTC](https://discuss.elastic.co/t/-all-like-multifield-field-can-be-defined-like--all-in-mappings/14277/6 "2017-07-06T02:08:25Z")

</div>


