# Index Management supporting transform job as there action

**URL:** https://forum.opensearch.org/t/index-management-supporting-transform-job-as-there-action/27927
**Category:** Index Management
**Created:** [March 16, 2026, 9:48am UTC](https://forum.opensearch.org/t/index-management-supporting-transform-job-as-there-action/27927 "2026-03-16T09:48:46Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![gourabh09](https://avatars.discourse-cdn.com/v4/letter/g/958977/32.png) [@gourabh09](https://forum.opensearch.org/u/gourabh09)
#### Post date: [March 16, 2026, 9:48am UTC](https://forum.opensearch.org/t/index-management-supporting-transform-job-as-there-action/27927/1 "2026-03-16T09:48:46Z")

</div>

**Versions** (relevant - OpenSearch/Dashboard/Server OS/Browser):

**Describe the issue** : Our goal is to make a transform job that runs just one day before the deletion of index . currently working solution is the we can put let suppose min\_index age as 7d for deletion and in transform job what we can do is now-7d in data\_selection\_query but our objective is to make now-7d as dynamic it can now-{{retention\_period}} so we are trying to figure out the ways such that after a particular index age which can be anything we will run that particular transform job

---

<div class="post-metadata">

### Author: ![Anthony](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/anthony/32/9939_2.png) [@Anthony](https://forum.opensearch.org/u/Anthony)
#### Post date: [March 16, 2026, 11:47am UTC](https://forum.opensearch.org/t/index-management-supporting-transform-job-as-there-action/27927/2 "2026-03-16T11:47:41Z")

</div>

@gourabh09 The `data_selection_query` is parsed directly as a query DSL with no template compilation step, therefore `now-{{retention_period}}` or similar patterns won’t be evaluated.

The possible workaround would be:

1. Use the ISM API to programmatically update the policy (re-PUT the policy JSON with the correct date math) whenever your retention period changes.
2. Use date math directly in the query (`now-7d`) and update manually when retention changes.

I would recommend to open a github issue [here](https://github.com/opensearch-project/index-management) for this.

---

<div class="post-metadata">

### Author: ![gourabh09](https://avatars.discourse-cdn.com/v4/letter/g/958977/32.png) [@gourabh09](https://forum.opensearch.org/u/gourabh09)
#### Post date: [March 16, 2026, 1:50pm UTC](https://forum.opensearch.org/t/index-management-supporting-transform-job-as-there-action/27927/4 "2026-03-16T13:50:58Z")

</div>

@Anthony we will be changing the minimum index age to perform any action (example deletion) then based on that we need to data\_selection\_query in our transform job

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/3/33547ea01a5b12dcca2958411d3edd97ae2ea8c1.png) [@system](https://forum.opensearch.org/u/system)
#### Post date: [May 15, 2026, 1:51pm UTC](https://forum.opensearch.org/t/index-management-supporting-transform-job-as-there-action/27927/5 "2026-05-15T13:51:39Z")

</div>

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