From what I understand, I should be able to change a mapping from a string
to a multifield without conflict, but when I attempt to, I get a
MergeMappingException:
{
"error" : "MergeMappingException[Merge failed with failures {[mapper
[tags] of different type, current_type [string], merged_type
[MultiFieldMapper], mapper [tags.breakdown] of different type, current_type
[string], merged_type [MultiFieldMapper], mapper [tags.partial] of
different type, current_type [string], merged_type [MultiFieldMapper]]}]",
"status" : 400
}
Here's the existing mapping:
{
"items" : {
"properties" : {
"name" : {
"type" : "string"
},
"tags" : {
"type" : "multi_field",
"fields" : {
"tags" : {
"type" : "string",
"analyzer" : "tag_analyzer"
},
"breakdown" : {
"type" : "string",
"analyzer" : "breakdown_tag_analyzer",
"include_in_all" : false
},
"partial" : {
"type" : "string",
"index_analyzer" : "partial_tag_analyzer",
"search_analyzer" : "tag_analyzer",
"include_in_all" : false
}
}
}
}
}
}
And here's how I'd like to update it:
{
"items" : {
"properties" : {
"tags" : {
"type" : "multi_field",
"fields" : {
"tags" : {
"type" : "multi_field",
"path" : "just_name",
"fields" : {
"tags" : {"type" : "string", "analyzer" : "tag_analyzer"},
"tags_all" : {"type" : "string", "analyzer" : "tag_analyzer"}
},
"boost" : 1.0
},
"breakdown" : {
"type" : "multi_field",
"path" : "just_name",
"fields" : {
"breakdown" : {"type" : "string", "analyzer" :
"breakdown_tag_analyzer"},
"tags_all" : {"type" : "string", "analyzer" :
"breakdown_tag_analyzer"}
},
"boost" : 0.8
},
"partial" : {
"type" : "multi_field",
"path" : "just_name",
"fields" : {
"partial" : {
"type" : "string",
"index_analyzer" : "partial_tag_analyzer",
"search_analyzer" : "tag_analyzer"
},
"tags_all" : {
"type" : "string",
"index_analyzer" : "partial_tag_analyzer",
"search_analyzer" : "tag_analyzer"
}
}
}
}
}
}
}
}
Any idea why I'm getting the error or how to get around it? I'm working
with a finicky river to get this data, so I'd like to avoid having to
delete it and the index and set everything up again. (Even them, I'm not
sure I would be able to, as the river would create the mapping on its own,
and I'd end up with the same conflict again.)
Thanks,
Emily.
--
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.