Skip to content

Commit 5f8c0f8

Browse files
authored
OP: add RediSearch v2.10.6 release notes (#581)
1 parent 609b325 commit 5f8c0f8

File tree

1 file changed

+16
-1
lines changed

1 file changed

+16
-1
lines changed

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

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,11 +13,26 @@ weight: 91
1313
---
1414
## Requirements
1515

16-
RediSearch v2.8.15 requires:
16+
RediSearch v2.8.16 requires:
1717

1818
- Minimum Redis compatibility version (database): 7.2
1919
- Minimum Redis Enterprise Software version (cluster): 7.2.4
2020

21+
## v2.8.16 (August 2024)
22+
23+
This is a maintenance release for RediSearch 2.8
24+
25+
Update urgency: `HIGH` : There is a critical bug that may affect a subset of users. Upgrade!
26+
27+
- Bug fixes:
28+
29+
- [#4896](https://github.com/redisearch/redisearch/pull/4896) - `FT.AGGREGATE` with `VERBATIM` option is not handled by the shards in cluster mode (MOD-7463)
30+
- [#4917](https://github.com/redisearch/redisearch/pull/4917) - Union query, similar to `"is|the"`, starting with 2 [stopwords](https://redis.io/docs/latest/develop/interact/search-and-query/advanced-concepts/stopwords/) could cause a crash (MOD-7495)
31+
- [#4921](https://github.com/redisearch/redisearch/pull/4921) - Counting twice the field statistics at the `#search` section of an `INFO` response (MOD-7339)
32+
- [#4939](https://github.com/redisearch/redisearch/pull/4939) - Query warning when using RESP3 response for reaching `MAXPREFIXEXPANSION` (MOD-7588)
33+
- [#4930](https://github.com/redisearch/redisearch/pull/4930) - Loop when using the wildcard `w'term'` and prefix/infix/suffix pattern `'ter*'` leading shard to restart (MOD-7453)
34+
- [#4912](https://github.com/redisearch/redisearch/pull/4912) - Avoid stemming expansion when querying for numeric values (MOD-7025)
35+
2136
## v2.8.15 (July 2024)
2237

2338
Update urgency: `HIGH` : There is a critical bug that may affect a subset of users. Upgrade!

0 commit comments

Comments
 (0)