Include_in_all option being ignored

Nick_Hoffman · January 31, 2012, 12:53am

Hi guys. In a dynamic template, I've got a multi_field field with 2 fields:
"{name}", and "analyzed". The "analyzed" field is configured to be included
in _all . However, after indexing a document the "analyzed" field is
configured to not be included in _all .

I've written up a quick gist with the curl commands here:

gist.github.com

https://gist.github.com/nickhoffman/614309d5473552732379

1_setup.txt

# As you can see below, "bars.*.analyzed" is configured to be included in _all .

curl -X DELETE 'localhost:9200/test?pretty=true'
echo

curl -X PUT 'localhost:9200/test?pretty=true'
echo

curl -X PUT 'localhost:9200/test/item/_mapping?pretty=true' -d '
{

This file has been truncated. show original

2_get_mapping.txt

# The dynamic mapping says that analyzed fields in "bars" should be included in _all .
#
# However, getting the mapping shows that "bars.colour.analyzed" is NOT included in _all .

curl 'localhost:9200/test/item/_mapping?pretty=1'
{
  "item" : {
    "dynamic_templates" : [ {
      "string_property" : {
        "mapping" : {

This file has been truncated. show original

Any idea what's going on?

Thanks,
Nick

kimchy · January 31, 2012, 5:10pm

In multi field mapping, only the "main" filed can be included in all (or not), the others are really not relevant (since its the same text that gets added to all). Note, the _all field has its own analyzer.

On Tuesday, January 31, 2012 at 2:53 AM, Nick Hoffman wrote:

Hi guys. In a dynamic template, I've got a multi_field field with 2 fields: "{name}", and "analyzed". The "analyzed" field is configured to be included in _all . However, after indexing a document the "analyzed" field is configured to not be included in _all .

I've written up a quick gist with the curl commands here:
Why is "bars.colour.analyzed" not included in all? · GitHub

Any idea what's going on?

Thanks,
Nick

Nick_Hoffman · January 31, 2012, 7:00pm

On Tuesday, 31 January 2012 12:10:54 UTC-5, kimchy wrote:

In multi field mapping, only the "main" filed can be included in all (or
not), the others are really not relevant (since its the same text that gets
added to all). Note, the _all field has its own analyzer.

Ah, that'd explain it! Thanks for that.

Topic		Replies	Views
Question on searching in a custom generated field Elasticsearch	1	312	July 6, 2017
Always add a not_analyzed field to strings template mapping Elasticsearch	3	1374	July 5, 2017
Exclude meta-fileds from _all Elasticsearch	7	735	September 27, 2018
Experiencing problems using root object dynamic template mappings Elasticsearch	2	309	July 6, 2017
'_all' field for multi field data store occupying more space Elasticsearch	5	805	July 5, 2017

Include_in_all option being ignored

Related Topics