You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisstack/redisstack-7.4-release-notes.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,7 @@ This is a GA release of Redis Stack version 7.4.
68
68
### Headlines
69
69
**Data Structures**
70
70
71
-
`Hash`: Redis now supports expiration of individual hash fields. Redis already supports key expiration. For each key - users can specify a time when the key should expire, or alternatively - specify the remaining time-to-live (TTL) after which the key would expire. One very frequent request was to allow specifying expiration time or TTL also for individual hash fields, which is now supported using 9 new Redis commands:
71
+
`Hash`: Redis now supports expiration of individual hash fields. Redis already supports key expiration. For each key, users can specify a time when it should expire, or specify the remaining time-to-live (TTL) after which it would expire. One very frequent request was to allow specifying expiration time or TTL also for individual hash fields, which is now supported using nine new Redis commands:
72
72
-`HEXPIRE`, `HPEXPIRE`, `HEXPIREAT`, `HPEXPIREAT` - set the time when specific hash fields should expire, or the remaining time-to-live for specific fields.
73
73
-`HTTL`, `HPTTL`, `HEXPIRETIME`, `HPEXPIRETIME` - retrieve the time when specific hash fields should expire, or the remaining time-to-live for specific fields
74
74
-`HPERSIST` - remove the expiration of specific hash fields.
@@ -78,16 +78,16 @@ There are many additional improvements, including new command arguments, securit
78
78
79
79
`Time series`: The latest time series data structure adds a highly requested feature: insertion-filter for close samples. Many sensors report data periodically. Often, the difference between the measured value and the previously measured value is negligible and related to random noise or to measurement accuracy limitations. When both the time difference and the value difference between the current and the previous sample are small, it may be preferable to ignore (not to add) the new measurement.
80
80
81
-
`JSON`: Introduces a fix to not duplicate AOF commands multiple times in `JSON.MSET`.
81
+
`JSON`: Introduces a fix to avoid duplicating AOF commands multiple times in `JSON.MSET`.
82
82
83
83
`Probabilistic`: Now, an error is returned if `CMS.MERGE` results in an overflow or underflow.
84
84
85
85
**Search and query**
86
86
87
-
New `BFLOAT16` and `FLOAT16` vector data types, reducing memory consumed by vectors while preserving accuracy.
88
-
Support for indexing empty and missing values and enhanced developer experience for queries with exact matching capabilities.
89
-
Developers can now match `TAG` fields without needing to escape special characters, making the onboarding process and use of the query syntax simpler.
90
-
Geospatial search capabilities have been expanded with new `INTERSECT` and `DISJOINT` operators, and ergonomics have been improved by providing better reporting of the memory consumed by the index and exposing the Full-text scoring in the aggregation pipeline.
87
+
-New `BFLOAT16` and `FLOAT16` vector data types reduce memory consumed by vectors while preserving accuracy.
88
+
-Support for indexing empty and missing values and enhanced developer experience for queries with exact matching capabilities.
89
+
-Developers can now match `TAG` fields without needing to escape special characters, making the onboarding process and use of the query syntax simpler.
90
+
-Geospatial search capabilities have been expanded with new `INTERSECT` and `DISJOINT` operators, and ergonomics have been improved by providing better reporting of the memory consumed by the index and exposing the Full-text scoring in the aggregation pipeline.
0 commit comments