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

Elastic Stack Elasticsearch
1

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.
For more options, visit https://groups.google.com/groups/opt_out.

2

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 :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 6 nov. 2013 à 01:10, AlexR 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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

3

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 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 :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 6 nov. 2013 à 01:10, AlexR 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.
For more options, visit 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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

4

see mapping for all field in multifield-boost.json · GitHub
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 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 :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 6 nov. 2013 à 01:10, AlexR 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.
For more options, visit 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.
For more options, visit 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.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

5

Thanks a lot Alex!

-Amit.

On Wed, Nov 6, 2013 at 3:24 PM, Alex Roytman roytmana@gmail.com wrote:

see mapping for all field in multifield-boost.json · GitHub
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 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 :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 6 nov. 2013 à 01:10, AlexR 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.
For more options, visit 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.
For more options, visit 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.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.

For more options, visit 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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.