# ILM policy to transform index

**URL:** <https://discuss.elastic.co/t/ilm-policy-to-transform-index/256974>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management, transforms\
**Created:** [November 29, 2020, 5:36am UTC](https://discuss.elastic.co/t/ilm-policy-to-transform-index/256974 "2020-11-29T05:36:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![fadjar340](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fadjar340/32/43610_2.png) [@fadjar340](https://discuss.elastic.co/u/fadjar340)\
**Post date:** [November 29, 2020, 5:36am UTC](https://discuss.elastic.co/t/ilm-policy-to-transform-index/256974/1 "2020-11-29T05:36:26Z")

</div>

Is it possible to use ILM policy to the transform index result?  
I tried to the transform index and added alias into it, but the ILM not works as expected for transform indices.  
Is there any workaround to do this?

Regards,  
Fadjar340

---

<div class="post-metadata">

**Author:** ![Hendrik\_Muhs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hendrik_muhs/32/25802_2.png) [@Hendrik\_Muhs](https://discuss.elastic.co/u/Hendrik_Muhs)\
**Post date:** [November 30, 2020, 2:10pm UTC](https://discuss.elastic.co/t/ilm-policy-to-transform-index/256974/2 "2020-11-30T14:10:39Z")

</div>

Hi,

please have a look into [limitations](https://www.elastic.co/guide/en/elasticsearch/reference/current/transform-limitations.html#transform-ilm-destination).

ILM on the destination index may cause unexpected problems, because transform updates/overwrites documents. For example a rollover can lead to duplicates, see this [issue](https://github.com/elastic/elasticsearch/issues/61587).

As pointed out in limitations, consider using [date index name processor](https://www.elastic.co/guide/en/elasticsearch/reference/current/date-index-name-processor.html) to get ILM-like behavior if your transform contains a `date_histogram`.

Having that said, nobody prevents you from using ILM on the destination index, it just has the mentioned side-effects. You may be able to work-around them in your application (e.g. collapsing dups).

> [@fadjar340](#):
>
> I tried to the transform index and added alias into it, but the ILM not works as expected for transform indices.

Transform can write to aliases including a write alias. This seems like a bug or a misconfiguration of ILM. If you share more information (repro steps) we might be able to 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:** [December 28, 2020, 2:10pm UTC](https://discuss.elastic.co/t/ilm-policy-to-transform-index/256974/3 "2020-12-28T14:10:42Z")

</div>

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