# Updating field as index = true with large document set

**URL:** <https://discuss.elastic.co/t/updating-field-as-index-true-with-large-document-set/234731>\
**Category:** Elasticsearch\
**Created:** [May 28, 2020, 11:29am UTC](https://discuss.elastic.co/t/updating-field-as-index-true-with-large-document-set/234731 "2020-05-28T11:29:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Virajsl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/virajsl/32/48327_2.png) [@Virajsl](https://discuss.elastic.co/u/Virajsl)\
**Post date:** [May 28, 2020, 11:29am UTC](https://discuss.elastic.co/t/updating-field-as-index-true-with-large-document-set/234731/1 "2020-05-28T11:29:31Z")

</div>

I have large set of documents in index. Earlier some fields are mapped as index = false since client do not wanted to search on these. As per new changes certain fields needs to be set as searchable ( setting index = true ) . Is this recommended to do in production environment ( with put api ) ? Will this hurt cluster ?

Also if i want to add new field as and set it as index = true, would it effect performance of cluster ? How adding fields affect old data which does not have that fields ?

---

<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 25, 2020, 11:29am UTC](https://discuss.elastic.co/t/updating-field-as-index-true-with-large-document-set/234731/2 "2020-06-25T11:29:31Z")

</div>

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