Hi,
We're getting ready to perform an upgrade of an ES cluster from 1.7.5 to 2.4.6 (the index started off life on the 0.9.x series) and from running the migration checker I'm seeing a an error around "Search analyzer without index analyzer" in which a few fields on some older indices seem to have a search_analyzer but no index_anayzer (mapping snippet below):
"displayName": {
"type": "string",
"search_analyzer": "lowerKeyword"
}
Every attempt I've made at setting the index_analyzer and/or the analyzer are either generating mapping conflicts or being ignored silently. For example if I set the analyzer to 'default' it does not generate an error but nothing seems to actually change per a GET on the mapping.
Any help resolving this would be greatly appreciated,
-Lee