# Timestamp field support added in master branch **URL:** \ **Category:** Elasticsearch\ **Created:** [August 30, 2011, 7:31pm UTC](https://discuss.elastic.co/t/timestamp-field-support-added-in-master-branch/5283 "2011-08-30T19:31:35Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Benjamin\_Deveze](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benjamin_deveze/32/1577_2.png) [@Benjamin\_Deveze](https://discuss.elastic.co/u/Benjamin_Deveze)\ **Post date:** [August 30, 2011, 7:31pm UTC](https://discuss.elastic.co/t/timestamp-field-support-added-in-master-branch/5283/1 "2011-08-30T19:31:35Z")
Just a quick one to let you know that we have added the support for a timestamp field. If you want to play with it and test it you can find more details about it here: [https://github.com/elasticsearch/elasticsearch/issues/1285](https://github.com/elasticsearch/elasticsearch/issues/1285) It may seem a little addition but it will hopefully open the way to new cool features like ttl per docs, rolling indices... ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [August 30, 2011, 7:54pm UTC](https://discuss.elastic.co/t/timestamp-field-support-added-in-master-branch/5283/2 "2011-08-30T19:54:05Z")
Great job. How do the timestamps work in a distributed setup when not-externally defined? Time can be different between servers. I have seen system issues because two machines were 8 seconds apart! Might be a non-issue since the use cases where a failure might occur are very few. Ivan On Tue, Aug 30, 2011 at 3:31 PM, Benjamin Devèze [benjamin.deveze@gmail.com](mailto:benjamin.deveze@gmail.com) wrote: > Just a quick one to let you know that we have added the support for a > timestamp field. > If you want to play with it and test it you can find more details about it > here: [Timestamp field support · Issue #1285 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1285) > It may seem a little addition but it will hopefully open the way to new cool > features like ttl per docs, rolling indices... ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [August 30, 2011, 7:59pm UTC](https://discuss.elastic.co/t/timestamp-field-support-added-in-master-branch/5283/3 "2011-08-30T19:59:23Z")
The timestamp is "taken", if not defined, on the clustered node. So, time should be sync'ed (up to you to what degree) between the nodes when relying on automatic timestamp. On Tue, Aug 30, 2011 at 10:54 PM, Ivan Brusic [ivan@brusic.com](mailto:ivan@brusic.com) wrote: > Great job. > > How do the timestamps work in a distributed setup when not-externally > defined? Time can be different between servers. I have seen system > issues because two machines were 8 seconds apart! Might be a > non-issue since the use cases where a failure might occur are very > few. > > Ivan > > On Tue, Aug 30, 2011 at 3:31 PM, Benjamin Devèze > [benjamin.deveze@gmail.com](mailto:benjamin.deveze@gmail.com) wrote: > > > Just a quick one to let you know that we have added the support for a > > timestamp field. > > If you want to play with it and test it you can find more details about > > it > > here: [Timestamp field support · Issue #1285 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1285) > > It may seem a little addition but it will hopefully open the way to new > > cool > > features like ttl per docs, rolling indices... ---
**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, 3:55am UTC](https://discuss.elastic.co/t/timestamp-field-support-added-in-master-branch/5283/4 "2017-07-06T03:55:31Z")
Closed on July 6, 2017, 3:55am UTC