# Unable to update analyzer

**URL:** <https://discuss.elastic.co/t/unable-to-update-analyzer/99113>\
**Category:** Elasticsearch\
**Created:** [September 1, 2017, 10:37am UTC](https://discuss.elastic.co/t/unable-to-update-analyzer/99113 "2017-09-01T10:37:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kanchan](https://avatars.discourse-cdn.com/v4/letter/k/8797f3/32.png) [@kanchan](https://discuss.elastic.co/u/kanchan)\
**Post date:** [September 1, 2017, 10:37am UTC](https://discuss.elastic.co/t/unable-to-update-analyzer/99113/1 "2017-09-01T10:37:11Z")

</div>

Hi,  
I have used tokenizer as below:  
"text\_general\_likely\_new": {  
"tokenizer": "standard ",  
"filter": [  
"StopFilterFactory",  
"LowerCaseFilterFactory",  
"SynonymFilterFactory",  
"ASCIIFoldingFilterFactory"  
]  
}

But I think there was a space like "standard " while defining [tokenizer.So](http://tokenizer.So) it is showing error like:

{  
"error": {  
"root\_cause": [  
{  
"type": "exception",  
"reason": "Failed to verify index [historical\_new/QGeFAxAUS7qHd4NlgeC\_5g]"  
}  
],  
"type": "exception",  
"reason": "Failed to verify index [historical\_new/QGeFAxAUS7qHd4NlgeC\_5g]",  
"caused\_by": {  
"type": "illegal\_argument\_exception",  
"reason": "Custom Analyzer [text\_general\_likely] failed to find tokenizer under name [standard]"  
}  
},  
"status": 500  
}

Now I changed it without space like: "tokenizer": "standard" but still showing same error changes doesn't it.

Please let me know solution for it.

---

<div class="post-metadata">

**Author:** ![jimczi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jimczi/32/47985_2.png) [@jimczi](https://discuss.elastic.co/u/jimczi)\
**Post date:** [September 4, 2017, 9:29am UTC](https://discuss.elastic.co/t/unable-to-update-analyzer/99113/2 "2017-09-04T09:29:22Z")

</div>

Which version of es are you using ? There was a bug at some point that made any invalid updates to the setting of a closed index non recoverable. This was fixed in 5.4.1:

> <https://github.com/elastic/elasticsearch/pull/24487>

  
If you are on 5.x you should upgrade to the latest version: 5.5.2 which has the fix for this issue.

---

<div class="post-metadata">

**Author:** ![kanchan](https://avatars.discourse-cdn.com/v4/letter/k/8797f3/32.png) [@kanchan](https://discuss.elastic.co/u/kanchan)\
**Post date:** [September 4, 2017, 12:40pm UTC](https://discuss.elastic.co/t/unable-to-update-analyzer/99113/3 "2017-09-04T12:40:53Z")

</div>

Thanks..... I am using elasticsearch 5.3.0

---

<div class="post-metadata">

**Author:** ![jimczi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jimczi/32/47985_2.png) [@jimczi](https://discuss.elastic.co/u/jimczi)\
**Post date:** [September 4, 2017, 2:58pm UTC](https://discuss.elastic.co/t/unable-to-update-analyzer/99113/4 "2017-09-04T14:58:38Z")

</div>

Then you are affected by this bug and should upgrade to 5.5 which has a fix.

---

<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:** [October 2, 2017, 2:59pm UTC](https://discuss.elastic.co/t/unable-to-update-analyzer/99113/5 "2017-10-02T14:59:12Z")

</div>

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