content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.6-release-notes.md
RedisTimeSeries v1.6.19 requires:
This is a maintenance release for RedisTimeSeries 1.6.
Update urgency: MODERATE: Program an upgrade of the server, but it's not urgent.
Details:
Bug fixes:
This is a maintenance release for RedisTimeSeries 1.6.
Update urgency: HIGH: There is a critical bug that may affect a subset of users. Upgrade!
Details:
This is a maintenance release for RedisTimeSeries 1.6.
Update urgency: HIGH: There is a critical bug that may affect a subset of users. Upgrade!
Details:
Features:
Bug fixes:
TS.DEL]({{< relref "commands/ts.del" >}}), it may still be accessible with [TS.GET]({{< relref "commands/ts.get" >}})TS.MRANGE]({{< relref "commands/ts.mrange" >}}), [TS.MREVRANGE]({{< relref "commands/ts.mrevrange" >}}): on a multi-shard environment, some chunks may be skipped{{<note>}} New RDB version (v5). RDB files created with 1.6.16 are not backward compatible. {{</note>}}
This is a maintenance release for RedisTimeSeries 1.6.
Update urgency: HIGH: There is a critical bug that may affect a subset of users. Upgrade!
Details:
Bug fixes:
This is a maintenance release for RedisTimeSeries 1.6.
Update urgency: HIGH: There is a critical bug that may affect a subset of users. Upgrade!
Details:
Bug fixes:
This is a maintenance release for RedisTimeSeries 1.6.
Update urgency: MODERATE: Program an upgrade of the server, but it's not urgent.
Details:
Bug fixes:
RANGE]({{< relref "commands/ts.range" >}}), [REVRANGE]({{< relref "commands/ts.revrange" >}}), [MRANGE]({{< relref "commands/ts.mrange" >}}), and [MREVRANGE]({{< relref "commands/ts.mrevrange" >}}): Possibly incorrect result when using ALIGN and aggregating a bucket with a timestamp close to 0RANGE]({{< relref "commands/ts.range" >}}) and [REVRANGE]({{< relref "commands/ts.revrange" >}}) when argument parsing failsRANGE]({{< relref "commands/ts.range" >}}), [REVRANGE]({{< relref "commands/ts.revrange" >}}), [MRANGE]({{< relref "commands/ts.mrange" >}}), and [MREVRANGE]({{< relref "commands/ts.mrevrange" >}}): Using FILTER_BY_TS without specifying timestamps now returns an error as expectedThis is a maintenance release for RedisTimeSeries 1.6.
Update urgency: MODERATE: Program an upgrade of the server, but it's not urgent.
Details:
Security and privacy:
Bug fixes:
This is the General Availability release of RedisTimeSeries 1.6.
RedisTimeSeries 1.6 adds support for aggregating across multiple time series (multi-key). Before this version, queries such as "the maximum observed value of a set of time series" needed to be calculated client-side. Such queries can now be computed server-side, leveraging the heart of RedisGears (LibMR) for clustered databases.
Introduction of GROUPBY and REDUCE in TS.MRANGE and TS.MREVRANGE to add support for "multi-key aggregation" and support for such aggregations spanning multiple shards, leveraging LibMR. Currently, we support min, max, and sum as reducers and grouping by a label.
#722, #275 Filter results using FILTER_BY_TS by providing a list of timestamps and FILTER_BY_VALUE by providing a min and a max value (TS.RANGE, TS.REVRANGE, TS.MRANGE, and TS.MREVRANGE).
#603, #611, #841 Introduction of TS.DEL which allows deleting samples in a time series within two timestamps (inclusive).
#762 Limit the number of returned labels in the response of read commands (TS.MRANGE, TS.MREVRANGE, and TS.MGET) using SELECTED_LABELS. This can be a significant performance improvement when returning a large number of series.
#655, #801 Ability to align the aggregation buckets with the requested start, end, or specific timestamp on aggregation queries using ALIGN (TS.RANGE, TS.REVRANGE, TS.MRANGE, and TS.MREVRANGE).
#675 Add keyspace notifications for all CRUD commands. Check out this test for the details.
#882 Auto Tiering support.