# Coping with ES' Use of org.joda.time.MutableDateTime **URL:** \ **Category:** Elasticsearch\ **Created:** [October 17, 2018, 1:37am UTC](https://discuss.elastic.co/t/coping-with-es-use-of-org-joda-time-mutabledatetime/152733 "2018-10-17T01:37:46Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![SpaceMoose](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spacemoose/32/35972_2.png) [@SpaceMoose](https://discuss.elastic.co/u/SpaceMoose)\ **Post date:** [October 17, 2018, 11:28pm UTC](https://discuss.elastic.co/t/coping-with-es-use-of-org-joda-time-mutabledatetime/152733/4 "2018-10-17T23:28:22Z")
@spinscale--Thanks for the tip. I am aware that what I currently have is search-intensive. Another question I have is: is there some equivalent of a cron job that I could run periodically--say daily and presumably outside of peak hours--to update my time\_to\_closure statistic for an existing index? Also, while we're on the topic of time processing, do you have any advice regarding another of my recent posts? [[Scanning Window Search through Index?](https://discuss.elastic.co/t/scanning-window-search-through-index/152163)]([Scanning Window Search through Index?](https://discuss.elastic.co/t/scanning-window-search-through-index/152163) I'm still struggling with figuring out how to sweep through an index in time with a time coordinate--let's just call it t--whose value I control (say by updating in a loop) and comparing various time field values with t to determine things like what tickets are open at a given moment, and how long have they been open. Thanks and all the best... --- _[View the full topic](https://discuss.elastic.co/t/coping-with-es-use-of-org-joda-time-mutabledatetime/152733)._