# How to Handle Index Template Changes with Data Streams

**URL:** <https://discuss.elastic.co/t/how-to-handle-index-template-changes-with-data-streams/254273>\
**Category:** Elasticsearch\
**Created:** [November 4, 2020, 1:35pm UTC](https://discuss.elastic.co/t/how-to-handle-index-template-changes-with-data-streams/254273 "2020-11-04T13:35:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![BenB196](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benb196/32/83401_2.png) [@BenB196](https://discuss.elastic.co/u/BenB196)\
**Post date:** [November 4, 2020, 1:35pm UTC](https://discuss.elastic.co/t/how-to-handle-index-template-changes-with-data-streams/254273/1 "2020-11-04T13:35:49Z")

</div>

Hi All,

I was wondering if there is any guidance on handle index template changes with data streams. Currently with regular indexes the guidance seems to be add a version number to part of the index name (ie: 7.9.3 or x.y.z). However, there doesn't appear to be any guidance around doing this with data streams. I was wondering if anyone had any ideas for this?

---

<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:** [December 2, 2020, 1:36pm UTC](https://discuss.elastic.co/t/how-to-handle-index-template-changes-with-data-streams/254273/2 "2020-12-02T13:36:01Z")

</div>

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