Multi_field "just_name" behavior with nested docs


(Justin Treher) #1

Do you think this behavior is intentional? I have a standard object and a
nested object that both share the name key. I was under the impression that
since "categories" is setup as nested object, it would be out of conflict
with "sales_person.". However, all my sales_person.name values are being
analyzed with the categories.name analyzer (default keyword). Name_test is
indexed correctly and searches work correctly. You can see that the mapping
is identical for name and name_test.

mappings:
"sales_person":{
"type":"object",
"properties":{
"name":{
"type":"multi_field",
"path":"just_name",
"fields":{
"name":{
"type":"string",
"analyzer":"id_keyword",
},
"name_test":{
"type":"string",
"analyzer":"id_keyword",
}
}
}
}
}
},
"categories":{
"type":"nested"
,"properties":{
"name":{
"type":"multi_field"
,"path":"just_name"
,"fields":{
"name":{
"type":"string",
"analyzer":"keyword"
}
}
}
}

--
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.


(system) #2