# Transform destination index rollover

**URL:** <https://discuss.elastic.co/t/transform-destination-index-rollover/350578>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management, transforms, datastreams\
**Created:** [January 8, 2024, 12:23pm UTC](https://discuss.elastic.co/t/transform-destination-index-rollover/350578 "2024-01-08T12:23:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![veryelastic](https://avatars.discourse-cdn.com/v4/letter/v/9dc877/32.png) [@veryelastic](https://discuss.elastic.co/u/veryelastic)\
**Post date:** [January 8, 2024, 12:23pm UTC](https://discuss.elastic.co/t/transform-destination-index-rollover/350578/1 "2024-01-08T12:23:39Z")

</div>

Hello,

It has been a while (I think) since this question came up on here, so I thought I'd check whether the answer had changed or not.

I have a transform which produces consolidated data with a time-series element to it.

This data is currently being written out to one index, but since the volume of the data is significant and the retention requirement lengthy, I would like to roll the index over from time to time.

Ideally, I'd like to use a datastream to handle this but, historically, this has not been possible.

The next-best alternative answer I could find was to use an index with an ingest pipeline which uses the `date_index_name` processor ([as documented here](https://www.elastic.co/guide/en/elasticsearch/reference/current/date-index-name-processor.html)) and a standard ILM policy on the destination indices to handle tiering, etc.

Is the date\_index\_name method still the recommended method?

Many thanks!

---

<div class="post-metadata">

**Author:** ![przemekwitek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/przemekwitek/32/79526_2.png) [@przemekwitek](https://discuss.elastic.co/u/przemekwitek)\
**Post date:** [January 12, 2024, 7:57am UTC](https://discuss.elastic.co/t/transform-destination-index-rollover/350578/2 "2024-01-12T07:57:28Z")

</div>

> so I thought I'd check whether the answer had changed or not.

Unfortunately not, the data stream is still not allowed as a destination index.  
See documentation: [Transform limitations | Elasticsearch Guide [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/transform-limitations.html#transform-data-streams-destination)

So if you have an ingest-pipeline workaround that is working for you then that is the way to go.

---

<div class="post-metadata">

**Author:** ![veryelastic](https://avatars.discourse-cdn.com/v4/letter/v/9dc877/32.png) [@veryelastic](https://discuss.elastic.co/u/veryelastic)\
**Post date:** [January 12, 2024, 9:25am UTC](https://discuss.elastic.co/t/transform-destination-index-rollover/350578/3 "2024-01-12T09:25:38Z")

</div>

Thanks for the reply, and the confirmation.

---

<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:** [February 9, 2024, 9:26am UTC](https://discuss.elastic.co/t/transform-destination-index-rollover/350578/4 "2024-02-09T09:26:16Z")

</div>

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