GitHub user yezhizi added a comment to the discussion: TimeSeries Proposal
Our proposal doesn't include specific optimizations for deletion or modification operations (`TS.INCRBY`, `TS.DEL`). When users delete or modify source series, we needs to read all data in the corresponding bucket from source series, recalculate the aggregated values, and update them in downstream series. This may incur significant overhead. However, given that time-series data is typically 'append-only' in nature, operations that modify or delete already-written data are relatively uncommon, so I believe this is reasonable. Below is [InfluxDB's description](https://www.influxdata.com/what-is-time-series-data/) regarding time-series characteristics: > Immutability – Since time series data comes in time order, it is almost > always recorded in a new entry, and as such, should be immutable and > append-only (appended to the existing data). GitHub link: https://github.com/apache/kvrocks/discussions/3044#discussioncomment-13718585 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
