-
Notifications
You must be signed in to change notification settings - Fork 274
Redis feature set table #1008
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redis feature set table #1008
Changes from 6 commits
3a52ed5
6583053
fc2f364
124fc14
c0c5837
bf02b8b
dcff44b
3c2677b
c2a10c3
f2d675e
002c69a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| A Redis feature set includes a specific Redis database version along with the advanced capabilities and data structures provided by compatible module versions. | ||
|
||
|
|
||
| To use a new feature introduced in a later feature set, you must upgrade the corresponding components according to the following table. | ||
|
|
||
| | Redis feature set | What's new | | ||
| |-------------------|------------| | ||
| | **Feature set version:** 7.4<br /><br />**Component versions:**<br />[Redis 7.4]({{<relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce/redisce-7.4-release-notes.md">}})<br />[Search 2.10]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.10-release-notes.md" >}})<br />[JSON 2.8]({{<relref "operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.8-release-notes.md">}})<br />[Time series 1.12]({{<relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.12-release-notes.md">}})<br />[Bloom 2.8]({{<relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.8-release-notes.md">}}) | **Hash**: <br>- [Expiration of individual hash fields]({{<relref "/develop/data-types/hashes#field-expiration">}}). <br> **Streams**: <br>- To start reading from the last stream message, use [`XREAD`]({{<relref "/commands/xread">}}) with the new ID value `+`.<br> **Time series**: <br>Insertion-filter for close samples. <br> **JSON**: <br>- A fix to not duplicate `AOF` commands multiple times in [`JSON.MSET`]({{< baseurl >}}/commands/json.mset/). <br> **Probabilistic**: <br>- Returns an error if [`CMS.MERGE`]({{< baseurl >}}/commands/cms.merge/) results in an overflow or underflow. <br> **Redis Query Engine**: <br>- New `BFLOAT16` and `FLOAT16` vector data types, reducing memory consumed by vectors while preserving accuracy. <br>- Support for indexing empty and missing values and enhanced developer experience for queries with exact matching capabilities. <br>- You can match `TAG` fields without needing to escape special characters. <br>- Expanded geospatial search with new `INTERSECT` and `DISJOINT` operators, improved reporting of the memory consumed by the index, and exposed full-text scoring in aggregation pipelines. <br> **Compatibility changes**: <br>- Redis feature set 7.4 does not include [triggers and functions]({{<relref "/operate/oss_and_stack/stack-with-enterprise/deprecated-features/triggers-and-functions">}}). To ensure a seamless upgrade, remove any T&F functions created before loading an RDB file into the new Redis Stack. | | ||
| | **Feature set version:** 7.2<br /><br />**Component versions:**<br />[Redis 7.2](https://raw.githubusercontent.com/redis/redis/7.2/00-RELEASENOTES)<br />[Search 2.8]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.8-release-notes.md" >}})<br />[JSON 2.6]({{<relref "operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.6-release-notes.md">}})<br />[Time series 1.10]({{<relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.10-release-notes.md">}})<br />[Bloom 2.6]({{<relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.6-release-notes.md">}})<br />[Gears 2.0](https://github.com/RedisGears/RedisGears/releases) | - New [`WAITAOF`]({{<relref "/commands/waitaof">}}) command.<br />- Memory and speed optimizations for lists, sets, and sorted sets.<br />- RESP3 support.<br />- New RDB file format.<br />**JSON**:<br />- New JSON commands.<br />**Redis Query Engine:**<br />- Geo polygon search.<br />- Performance improvements for sorted search and queries. | | ||
|
||
| | **Feature set version:** 6.2<br /><br />**Component versions:**<br />[Redis 6.2](https://raw.githubusercontent.com/redis/redis/6.2/00-RELEASENOTES)<br />[Search 2.6]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.6-release-notes.md" >}})<br />[JSON 2.4]({{<relref "operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.4-release-notes.md">}})<br />[Time series 1.8]({{<relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.8-release-notes.md">}})<br />[Bloom 2.4]({{<relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.4-release-notes.md">}})<br />[Graph 2.10]({{<relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.10-release-notes.md">}}) | **Time series**:<br />- Time series gap filling.<br />**JSON**:<br />- Improved JSON path parser.<br />**Probabilistic:**<br />- New probabilistic data structure t-digest.<br />**Redis Query Engine:**<br />- Wildcard queries for `TEXT` and `TAG`.<br />- Suffix search.<br />- Multi-value indexing and queries.<br />**Graph**:<br />- New pathfinding algorithms for graphs. | | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a caveat here: Redis CE doesn't include the advanced capabilities by default. Customers will either have to download and install them separately, or use Redis Stack. This, of course, will go away when CE8 ships, essentially replacing both standalone Redis CE and Redis Stack.
So, really, this just applies to RS, RC, and Redis Stack.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest using something like this to not mention advanced capabilities and data structures to be ready for CE8.
A Redis feature set represents the complete set of features available in a specific configuration, and its version number increments whenever a new feature is introduced.
To use a new feature introduced in a later feature set, you must upgrade to the corresponding feature set version, as outlined in the table below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct. We can add that in if you like. I don't think users are consuming modules separately often. We see in the field customers running redis-stack in production
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rrelledge , what do you think about this wording?
A Redis feature set represents the complete set of features available in a specific configuration, and its version number increments whenever a new feature is introduced.
To use a new feature introduced in a later feature set, you must upgrade to the corresponding feature set version, as outlined in the table below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ViktarStarastsenka
I'm fine with changing the feature set description, but I'm not sure about the phrase "specific configuration".
What do you think of something like:
"A Redis feature set represents the complete set of features available for a specific Redis version."
I don't think it's necessary to explain "its version number increments whenever a new feature is introduced".
I changed the last sentence to: "To use a new feature introduced in a later feature set, you must upgrade the corresponding components according to the following table."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, specific configuration sounds like something different than version.