# Making a new field indexable on a index under rollover policy

**URL:** <https://discuss.elastic.co/t/making-a-new-field-indexable-on-a-index-under-rollover-policy/282931>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [August 31, 2021, 1:44pm UTC](https://discuss.elastic.co/t/making-a-new-field-indexable-on-a-index-under-rollover-policy/282931 "2021-08-31T13:44:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Baygon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/baygon/32/91792_2.png) [@Baygon](https://discuss.elastic.co/u/Baygon)\
**Post date:** [August 31, 2021, 1:44pm UTC](https://discuss.elastic.co/t/making-a-new-field-indexable-on-a-index-under-rollover-policy/282931/1 "2021-08-31T13:44:30Z")

</div>

Hi,

We have an index under rollover policy/index template for which we need to update the mapping to make a field searchable (initially set up to index: false but now needed).

What would be the right process?

I'm thinking of the following process:

1. change the index template with the new mapping
2. manually force a rollover
3. reindex previous rollover indexes instances  
Would that make the new indexed field searchable on the new records? or would that break because old records are not searchable?

or should I create a new index, policy, template, then move my pipeline to this new correct format, and reindex the existing data into indexes matching the new rollover pattern?  
Like starting the first rollover index at xxxx-000025 and reindexing in all numbers below 25 ?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 1, 2021, 12:43am UTC](https://discuss.elastic.co/t/making-a-new-field-indexable-on-a-index-under-rollover-policy/282931/2 "2021-09-01T00:43:14Z")

</div>

Up to you what approach to take, they will both work and there's no set guidelines around it 🙂

---

<div class="post-metadata">

**Author:** ![Baygon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/baygon/32/91792_2.png) [@Baygon](https://discuss.elastic.co/u/Baygon)\
**Post date:** [September 1, 2021, 2:01am UTC](https://discuss.elastic.co/t/making-a-new-field-indexable-on-a-index-under-rollover-policy/282931/3 "2021-09-01T02:01:09Z")

</div>

Thanks, first option being the less disruptive, would that make the only new indexed field searchable on the new records? or would search queries break because old records are not searchable?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 1, 2021, 2:07am UTC](https://discuss.elastic.co/t/making-a-new-field-indexable-on-a-index-under-rollover-policy/282931/4 "2021-09-01T02:07:13Z")

</div>

It'll only apply to newly indexed data, not the existing data, yep.

---

<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:** [September 29, 2021, 2:07am UTC](https://discuss.elastic.co/t/making-a-new-field-indexable-on-a-index-under-rollover-policy/282931/5 "2021-09-29T02:07:40Z")

</div>

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