# "Search analyzer without index analyzer" migration tool error

**URL:** <https://discuss.elastic.co/t/search-analyzer-without-index-analyzer-migration-tool-error/121912>\
**Category:** Elasticsearch\
**Created:** [February 28, 2018, 6:02pm UTC](https://discuss.elastic.co/t/search-analyzer-without-index-analyzer-migration-tool-error/121912 "2018-02-28T18:02:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kohner86](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kohner86/32/28260_2.png) [@kohner86](https://discuss.elastic.co/u/kohner86)\
**Post date:** [February 28, 2018, 6:02pm UTC](https://discuss.elastic.co/t/search-analyzer-without-index-analyzer-migration-tool-error/121912/1 "2018-02-28T18:02:49Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![kohner86](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kohner86/32/28260_2.png) [@kohner86](https://discuss.elastic.co/u/kohner86)\
**Post date:** [March 1, 2018, 1:30pm UTC](https://discuss.elastic.co/t/search-analyzer-without-index-analyzer-migration-tool-error/121912/2 "2018-03-01T13:30:22Z")

</div>

We were able to figure it out, turns our its a false positive in the migration checker. At some point in the past there was a bug in ES 2.x:

> <https://github.com/elastic/elasticsearch/issues/14383>

The migration checker is looking for mappings which would trip up this bug, but the bug has since been fixed meaning the error the migration tool reports is not really an error. We ran as test upgrade and the upgraded server came online fine without resolving the mapping issue.

-Lee

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 29, 2018, 1:30pm UTC](https://discuss.elastic.co/t/search-analyzer-without-index-analyzer-migration-tool-error/121912/3 "2018-03-29T13:30:45Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.