DEV+RS: hash field limitation in RediSearch v2.10

Author: dwdougherty

content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.10-release-notes.md

@@ -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, expired fields may still be included in the query results, leading to potentially incorrect or inconsistent results.
 {{< /note >}}

content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisstack/redisstack-7.4-release-notes.md

@@ -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, 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.