# @timestamp field in a datastream

**URL:** https://discuss.elastic.co/t/timestamp-field-in-a-datastream/252258
**Category:** Elasticsearch
**Created:** [October 15, 2020, 7:15pm UTC](https://discuss.elastic.co/t/timestamp-field-in-a-datastream/252258 "2020-10-15T19:15:41Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![MichaelKopaniov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michaelkopaniov/32/77294_2.png) [@MichaelKopaniov](https://discuss.elastic.co/u/MichaelKopaniov)
#### Post date: [October 15, 2020, 7:15pm UTC](https://discuss.elastic.co/t/timestamp-field-in-a-datastream/252258/1 "2020-10-15T19:15:41Z")

</div>

Hi,

I'm currently examining the migration of an old ES cluster into an ILM managed [https://www.elastic.co/guide/en/elasticsearch/reference/master/data-streams.html](https://datastreams).

I do not fully understand the role of the required @timestamp field.  
I understand that writes are being directed to the write index while reads are being directed to all backing index. If writes are going to the current write index anyway, why does ES cares about the @timestamp field at all?

---

<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: [November 12, 2020, 7:15pm UTC](https://discuss.elastic.co/t/timestamp-field-in-a-datastream/252258/2 "2020-11-12T19:15:43Z")

</div>

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