# Best way to manage updates in timeseries data

**URL:** <https://discuss.elastic.co/t/best-way-to-manage-updates-in-timeseries-data/189107>\
**Category:** Elasticsearch\
**Created:** [July 5, 2019, 1:07pm UTC](https://discuss.elastic.co/t/best-way-to-manage-updates-in-timeseries-data/189107 "2019-07-05T13:07:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![matd](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matd/32/9892_2.png) [@matd](https://discuss.elastic.co/u/matd)\
**Post date:** [July 5, 2019, 1:07pm UTC](https://discuss.elastic.co/t/best-way-to-manage-updates-in-timeseries-data/189107/1 "2019-07-05T13:07:20Z")

</div>

Hi folks,

I'm dealing with geo-timeseries data (IOT use-case). The data is indexed in an ES and queried in various ways.  
So far, so good, but we have some bad data points (that we detect using outlier detection algorithms, heuristics, or even manual annotation), that we need to UPDATE. Sometimes, we just flag the data, other times, we do some [imputation](https://en.wikipedia.org/wiki/Imputation_(statistics)) to keep aggregates working well.

I'm not very fond of UPDATING what should be otherwise immutable data. This causes other complexities in the architecture, or when re-indexing. So I'm looking for design recommendations, REX, best practices, to deal with this kind of problematic.

Any pointer or comment will be appreciated !  
Thanks

Mat

---

<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:** [August 2, 2019, 1:07pm UTC](https://discuss.elastic.co/t/best-way-to-manage-updates-in-timeseries-data/189107/2 "2019-08-02T13:07:23Z")

</div>

Closed on August 2, 2019, 1:07pm UTC

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