Redis feature set table #1008
+26
−2
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 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. | ||
|
There was a problem hiding this comment. The suggestion is to locate the feature sets under the “Commands” section since basically commands are introduced or their behavior is changed with the feature sets There was a problem hiding this comment. I don't think we can easily include a separate, non-command page under the commands section at this time. The commands section uses layouts that work differently from the rest of the site. It did not work at all when I made a cursory attempt in my local env. I don't think it's a simple change, and we definitely want to be careful with the commands section. cc @dwdougherty since you are more familiar with the commands section than me. |
||
|
|
||
| A database is not compatible with module versions from different feature set versions. If you want to use advanced capability features or data structures introduced by a later feature set version, you must upgrade your database to the compatible Redis version and module versions according to the following table. | ||
|
|
||
| | Redis feature set version | Distributed in | What's new | | ||
|
There was a problem hiding this comment. maybe we do not actually need the "Distributed in" column at all - we can reference the feature set version from everywhere (e.g. release notes in RS, Redis Cloud, etc.) though I'd suggest creating a separate "Compatible versions" column, where we describe the Redis server version and modules (and just the Redis version with CE8) There was a problem hiding this comment. @ViktarStarastsenka I updated the staged previews of the table with your suggested changes. I also added the table to the Cloud changelog: https://redis.io/docs/staging/DOC-4673/operate/rc/changelog/ |
||
| |-------------------|----------------|------------| | ||
| | 7.4 | [Redis Cloud]({{<relref "/operate/rc">}})<br />[Redis Software]({{<relref "/operate/rs">}}) 7.8.x<br />[Redis Stack]({{<relref "/operate/oss_and_stack">}}) 7.4.x<br />[Redis Community Edition]({{<relref "/operate/oss_and_stack">}}) 7.4.x | Hash field expiration; new vector data types; time series insertion filters<br /><br />Compatible 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">}}) | | ||
| | 7.2 | [Redis Cloud]({{<relref "/operate/rc">}})<br />[Redis Software]({{<relref "/operate/rs">}}) 7.2.x-7.8.x<br />[Redis Stack]({{<relref "/operate/oss_and_stack">}}) 7.2.x<br />[Redis OSS]({{<relref "/operate/oss_and_stack">}}) 7.2.x | `WAITAOF`; memory and speed optimizations for lists, sets, and sorted sets; RESP3 support; new RDB file format; geo polygon search; performance improvements for sorted search and queries; new JSON commands<br /><br />Compatible 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) | | ||
| | 6.2 | [Redis Cloud]({{<relref "/operate/rc">}})<br />[Redis Software]({{<relref "/operate/rs">}}) 6.2.x-7.8.x<br />[Redis Stack]({{<relref "/operate/oss_and_stack">}}) 6.2.x<br />[Redis OSS]({{<relref "/operate/oss_and_stack">}}) 6.2.x | Wildcard queries for `TEXT` and `TAG`; suffix search; multi-value indexing and queries; improved JSON path parser; new probabilistic data structure t-digest; new pathfinding algorithms for graphs; time series gap filling<br /><br />Compatible 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">}}) | | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.