# Ask for best practice how to add new plugin analyzer to existing index (new field)

**URL:** <https://discuss.elastic.co/t/ask-for-best-practice-how-to-add-new-plugin-analyzer-to-existing-index-new-field/291589>\
**Category:** Elasticsearch\
**Created:** [December 13, 2021, 6:05am UTC](https://discuss.elastic.co/t/ask-for-best-practice-how-to-add-new-plugin-analyzer-to-existing-index-new-field/291589 "2021-12-13T06:05:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![garyzjq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/garyzjq/32/95099_2.png) [@garyzjq](https://discuss.elastic.co/u/garyzjq)\
**Post date:** [December 13, 2021, 6:05am UTC](https://discuss.elastic.co/t/ask-for-best-practice-how-to-add-new-plugin-analyzer-to-existing-index-new-field/291589/1 "2021-12-13T06:05:11Z")

</div>

(ES 7.15)

Hi teams,

For custom analyzer (defined in Index setting as json format) , I saw there were 2 best practices:

1. If want to add a new custom analyzer to existing index, need to close/re-open this index.
2. If there's no new analyzer introduced, we can add a new field with existing analyzer online, without closing the index.

On the other side, I can't find such best practice how to add a plugin analyzer to an existing index.

My question is **for a new analyzer plugin, after we deploy it to all nodes and make sure all nodes are restarted with this plugin, do we still need to close and re-open existing indices ? or we can directly add a new field with this new analyzer in existing index after the whole ES cluster restarted.**

Appreciate for your suggestions/ comments! Thanks.

Regards,  
Gary

---

<div class="post-metadata">

**Author:** ![garyzjq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/garyzjq/32/95099_2.png) [@garyzjq](https://discuss.elastic.co/u/garyzjq)\
**Post date:** [December 14, 2021, 11:10am UTC](https://discuss.elastic.co/t/ask-for-best-practice-how-to-add-new-plugin-analyzer-to-existing-index-new-field/291589/2 "2021-12-14T11:10:52Z")

</div>

ping for this topic

---

<div class="post-metadata">

**Author:** ![garyzjq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/garyzjq/32/95099_2.png) [@garyzjq](https://discuss.elastic.co/u/garyzjq)\
**Post date:** [December 17, 2021, 4:09pm UTC](https://discuss.elastic.co/t/ask-for-best-practice-how-to-add-new-plugin-analyzer-to-existing-index-new-field/291589/3 "2021-12-17T16:09:46Z")

</div>

ping again to see any chance to get help

---

<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:** [January 14, 2022, 4:10pm UTC](https://discuss.elastic.co/t/ask-for-best-practice-how-to-add-new-plugin-analyzer-to-existing-index-new-field/291589/4 "2022-01-14T16:10:16Z")

</div>

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