You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
but the second time curl -XPUT -d @mapping.json http://localhost:9200/twitter/foobar/_mapping
{"error":"MergeMappingException[Merge failed with failures {[mapper [description] has different index_analyzer, mapper [description] has different search_analyzer]}]","status":400}
with this mapping instead there's no problem posting it over and over
Just submitted PR #7902. Looks like there's only one point where null index analyzers and "default"-named index analyzers were being treated as nonequivalent.
Fixed behaviour where two representations of the default index analyzer weren't being treated as equivalent. Added REST test to confirm fix.
Closes#2716
Seems like reposting a mapping explicitly mentioning the default analyzer throws an error when it should not
with the following mapping.json
putting the mapping the 1st time everything goes well
curl -XPUT -d @mapping.json http://localhost:9200/twitter/foobar/_mapping
but the second time
curl -XPUT -d @mapping.json http://localhost:9200/twitter/foobar/_mapping
with this mapping instead there's no problem posting it over and over
so seems like for some reason the default analyzer is not considered to be equal to itself
The text was updated successfully, but these errors were encountered: