# Updating existing mapping to add custom analyzer in Elasticsearch 6.7

**URL:** <https://discuss.elastic.co/t/updating-existing-mapping-to-add-custom-analyzer-in-elasticsearch-6-7/235108>\
**Category:** Elasticsearch\
**Created:** [June 1, 2020, 4:40am UTC](https://discuss.elastic.co/t/updating-existing-mapping-to-add-custom-analyzer-in-elasticsearch-6-7/235108 "2020-06-01T04:40:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![username1234](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/username1234/32/69446_2.png) [@username1234](https://discuss.elastic.co/u/username1234)\
**Post date:** [June 1, 2020, 4:40am UTC](https://discuss.elastic.co/t/updating-existing-mapping-to-add-custom-analyzer-in-elasticsearch-6-7/235108/1 "2020-06-01T04:40:52Z")

</div>

Hello,

I have an existing index on Elasticsearch 6.7 that I would like to update the mappings on. On a test instance of Elasticsearch 6.7, I set up the index with the mapping and attempted a PUT call to update the mapping. However, I'm running into this error:

`{"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"analyzer [street1_analyzer] not found for field [no_stop_words]"}],"type":"mapper_parsing_exception","reason":"analyzer [street1_analyzer] not found for field [no_stop_words]"},"status":400}`

Is adding a custom analyzer and using it in a multi-field (of an existing property) not supported when updating an existing index? So far, I've only found [these restrictions](https://www.elastic.co/guide/en/elasticsearch/reference/6.8/indices-put-mapping.html#updating-field-mappings) on the ES documentation that closest matches the version of Elasticsearch that I am running.

I did a separate test where I created a new index with the mapping updates that I want from scratch (with the same multi-fields and analyzers), and I was successful in doing that. So I'm not sure if this is a restriction or there is some other error.

Additionally, if you add a multi-field that is analyzed differently to an index with a lot of existing documents, does it suffer any performance issues when using that multi-field? How does Elasticsearch treat that data?

---

<div class="post-metadata">

**Author:** ![username1234](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/username1234/32/69446_2.png) [@username1234](https://discuss.elastic.co/u/username1234)\
**Post date:** [June 2, 2020, 10:49pm UTC](https://discuss.elastic.co/t/updating-existing-mapping-to-add-custom-analyzer-in-elasticsearch-6-7/235108/2 "2020-06-02T22:49:32Z")

</div>

I'm going to guess that the answer on [this post](https://discuss.elastic.co/t/add-analyzer-to-existing-fields-in-index/78290) still applies for version 6.7.

---

<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:** [June 30, 2020, 10:49pm UTC](https://discuss.elastic.co/t/updating-existing-mapping-to-add-custom-analyzer-in-elasticsearch-6-7/235108/3 "2020-06-30T22:49:41Z")

</div>

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