Skip to content

Commit

Permalink
DEV+RS: hash field limitation in RediSearch v2.10 (#986)
Browse files Browse the repository at this point in the history
* DEV+RS: hash field limitation in RediSearch v2.10

* Corrections

* DOC-4670 Copy HFE known limitation to RS 7.8.x release notes

* DOC-4670 Updated HFE known limitation wording in RS 7.8.x release notes

---------

Co-authored-by: Rachel Elledge <[email protected]>
  • Loading branch information
dwdougherty and rrelledge authored Dec 23, 2024
1 parent 97bb16a commit f1b5a43
Show file tree
Hide file tree
Showing 5 changed files with 17 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -84,4 +84,5 @@ Improvements (since 2.10.4):
- The version inside Redis will be 2.10.5 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a Release Candidate flag.
- Minimal Redis version: 7.4
- If indexing and querying RedisJSON data structures, this version is best combined with RedisJSON 2.8 (v2.8.2 onwards)
- If one or more fields of a hash key expire after a query begins (using FT.SEARCH or FT.AGGREGATE), Redis does not account for these lazily expired fields. As a result, keys with expired fields may still be included in the query results, leading to potentially incorrect or inconsistent results.
{{< /note >}}
Original file line number Diff line number Diff line change
Expand Up @@ -89,6 +89,10 @@ There are many additional improvements, including new command arguments, securit
- Developers can now match `TAG` fields without needing to escape special characters, making the onboarding process and use of the query syntax simpler.
- 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.

{{< warning >}}
If one or more fields of a hash key expire after a query begins (using FT.SEARCH or FT.AGGREGATE), Redis does not account for these lazily expired fields. As a result, keys with expired fields may still be included in the query results, leading to potentially incorrect or inconsistent results.
{{< /warning >}}

**Removal of triggers and functions**

Redis Stack 7.4 will no longer include triggers and functions. To ensure a seamless upgrade, remove any T&F functions created before loading an RDB file into the new Redis Stack.
Expand Down
4 changes: 4 additions & 0 deletions content/operate/rs/release-notes/rs-7-8-releases/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -246,3 +246,7 @@ The following legacy UI features are not yet available in the new Cluster Manage
#### RedisGraph prevents upgrade to RHEL 9

You cannot upgrade from a prior RHEL version to RHEL 9 if the Redis Software cluster contains a RedisGraph module, even if unused by any database. The [RedisGraph module has reached end-of-life](https://redis.com/blog/redisgraph-eol/) and is completely unavailable in RHEL 9.

#### Query results might include hash keys with lazily expired fields

If one or more fields of a hash key expire after an `FT.SEARCH` or `FT.AGGREGATE` query begins, Redis does not account for these lazily expired fields. As a result, keys with expired fields might still be included in the query results, leading to potentially incorrect or inconsistent results.
Original file line number Diff line number Diff line change
Expand Up @@ -423,6 +423,10 @@ The following legacy UI features are not yet available in the new Cluster Manage

You cannot upgrade from a prior RHEL version to RHEL 9 if the Redis Software cluster contains a RedisGraph module, even if unused by any database. The [RedisGraph module has reached End-of-Life](https://redis.com/blog/redisgraph-eol/) and is completely unavailable in RHEL 9.

#### Query results might include hash keys with lazily expired fields

If one or more fields of a hash key expire after an `FT.SEARCH` or `FT.AGGREGATE` query begins, Redis does not account for these lazily expired fields. As a result, keys with expired fields might still be included in the query results, leading to potentially incorrect or inconsistent results.

## Security

#### Open source Redis security fixes compatibility
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -117,6 +117,10 @@ The following legacy UI features are not yet available in the new Cluster Manage

You cannot upgrade from a prior RHEL version to RHEL 9 if the Redis Software cluster contains a RedisGraph module, even if unused by any database. The [RedisGraph module has reached End-of-Life](https://redis.com/blog/redisgraph-eol/) and is completely unavailable in RHEL 9.

#### Query results might include hash keys with lazily expired fields

If one or more fields of a hash key expire after an `FT.SEARCH` or `FT.AGGREGATE` query begins, Redis does not account for these lazily expired fields. As a result, keys with expired fields might still be included in the query results, leading to potentially incorrect or inconsistent results.

## Security

#### Open source Redis security fixes compatibility
Expand Down

0 comments on commit f1b5a43

Please sign in to comment.