# TRANSFORM Destination index is not using Index Template

**URL:** <https://discuss.elastic.co/t/transform-destination-index-is-not-using-index-template/384611>\
**Category:** Elasticsearch\
**Tags:** transforms\
**Created:** [January 19, 2026, 6:14am UTC](https://discuss.elastic.co/t/transform-destination-index-is-not-using-index-template/384611 "2026-01-19T06:14:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tusharnemade](https://avatars.discourse-cdn.com/v4/letter/t/67e7ee/32.png) [@tusharnemade](https://discuss.elastic.co/u/tusharnemade)\
**Post date:** [January 19, 2026, 6:14am UTC](https://discuss.elastic.co/t/transform-destination-index-is-not-using-index-template/384611/1 "2026-01-19T06:14:18Z")

</div>

Hello Team,

> We are using Elasticsearch 7.8.0 version. I understand its very old [w are in process of upgradation too]
> 
> While using TRANSFORM feature , I am finding that my destination index is not using template settings of having primary shards = 5.
> 
> Could you please help me. how to fix this.
> 
> `curl -XPUT "/_transform/my_dau_trans?pretty" -H 'Content-Type: application/json' -d ' { "source": { "index": "appdetail-000001" }, "dest": { "index": "agg-jcappdtl-mydau-transform" }, "pivot": { "group_by": { "event_date": { "date_histogram": { "field": "timeStamp", "calendar_interval": "1d" } }, "appId_long": { "terms": { "field": "appId" } }, "platform": { "terms": { "field": "deviceInfo.platformType.keyword" } } }, "aggregations": { "active_users": { "cardinality": { "field": "accountId" } } } } }' -u $ES_USER:$ES_PASS`
> 
> My Template :
> 
> `curl -X PUT "/_index_template/appdt_transform?pretty" -H 'Content-Type: application/json' -d' { "index_patterns": ["agg-jcappdtl*transform"], "priority": 500, "template": { "settings": { "number_of_shards": 5, "number_of_replicas": 1 } } } ' -u $ES_USER:$ES_PASS`

---

<div class="post-metadata">

**Author:** ![Tortoise](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tortoise/32/147587_2.png) [@Tortoise](https://discuss.elastic.co/u/Tortoise)\
**Post date:** [January 19, 2026, 7:29am UTC](https://discuss.elastic.co/t/transform-destination-index-is-not-using-index-template/384611/2 "2026-01-19T07:29:20Z")

</div>

Hello @tusharnemade

This seems to be known issue & found below relevant github open issue :

> <https://github.com/elastic/elasticsearch/issues/118512>
>
> \### Description
> 
> Currently the destination index created for transform does not …respect the number of replicas and shards defined in the template that matches the index pattern, it will always default to 1 shard, 1 replica and using auto expand replicas as 0-1.
> 
> This adds an extra step of having to create the destination index before starting the transform, this should've been required.
> 
> When creating a transform the number of shards and replicas defined in the template should be respected.

As shared above we might have to create the transform index in advance with settings needed post which the transform will have the primary shards per requirement else it will be 1 primary shard & (0-1) auto expandable replicas.

Thanks!!
