# Maintain original timestamp across versions

**URL:** https://discuss.elastic.co/t/maintain-original-timestamp-across-versions/13037
**Category:** Elasticsearch
**Created:** [August 2, 2013, 12:05am UTC](https://discuss.elastic.co/t/maintain-original-timestamp-across-versions/13037 "2013-08-02T00:05:50Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![GivP](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/givp/32/2171_2.png) [@GivP](https://discuss.elastic.co/u/GivP)
#### Post date: [August 2, 2013, 12:05am UTC](https://discuss.elastic.co/t/maintain-original-timestamp-across-versions/13037/1 "2013-08-02T00:05:50Z")

</div>

I have enabled automatic \_timestamp on my indexes but every time an index  
is updated during a \_bulk request (or a regular update) the timestamp is  
also updated. This makes sense.

I want to know if there's a way to keep the original timestamp after an  
update? So we only ever see the timestamp for version 1 no matter how many  
times it is updated to a new version.

I have over 4 millions indexes and bulk update in chunks of 1000 so I'd  
rather not iterate through every single item to compare timestamps.

Any tips?

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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: [July 6, 2017, 2:23am UTC](https://discuss.elastic.co/t/maintain-original-timestamp-across-versions/13037/2 "2017-07-06T02:23:17Z")

</div>


