# Transform - Continuous mode for more than 1 index?

**URL:** https://discuss.elastic.co/t/transform-continuous-mode-for-more-than-1-index/239244
**Category:** Elasticsearch
**Created:** [June 30, 2020, 7:39am UTC](https://discuss.elastic.co/t/transform-continuous-mode-for-more-than-1-index/239244 "2020-06-30T07:39:43Z")
**Posts on this page:** 1
**Showing post:** 11

<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: [July 2, 2020, 11:32am UTC](https://discuss.elastic.co/t/transform-continuous-mode-for-more-than-1-index/239244/11 "2020-07-02T11:32:09Z")

</div>

The concept of a continuous transform is to continually increment and process checkpoints as new source data is ingested. The timestamp used for synchronizing `source` and `dest` **must** follow real time, meaning it must be a recent timestamp. To adjust for index delays, e.g. because the timestamp you use runs behind due to processing delays, you can use the `delay` parameter, default `60s`. That causes transform to deduct the delay when querying data, e.g. `lt now-delay`.

If you process historic data, there is no need to use a continuous transform, but you can use a batch transform. Is there a reason you want to process historic data but still use continuous mode?

There is a trick, instead of using the historic `timestamp`, you can add an ingest timestamp while you are feeding in new data, here is [how](https://discuss.elastic.co/t/dec-12th-2018-en-elasticsearch-automatically-adding-a-timestamp-to-documents/159314). You than use the ingest timestamp for `sync`, you can keep your `timestamp_max` and `timestamp_min` as is.

---

_[View the full topic](https://discuss.elastic.co/t/transform-continuous-mode-for-more-than-1-index/239244)._