RediSearch 2.8 release notes

RESP3 support. Geo Polygon Search. Performance improvements.

Requirements

RediSearch v2.8.30 requires:

• Minimum Redis compatibility version (database): 7.2
• Minimum Redis Enterprise Software version (cluster): 7.2.4

v2.8.30 (September 2025)

This is a maintenance release for RediSearch 2.8.

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

Bug fixes:

• #6672 Fix potential file descriptor leak when OOM.
• #6763 Fix potential deadlock during RDB loading in cases where the INFO command is sent to the server.

Full Changelog: https://github.com/RediSearch/RediSearch/compare/v2.8.29...v2.8.30.

v2.8.29 (August 2025)

This is a maintenance release for RediSearch 2.8.

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

Bug fixes:

• #6599 FLUSHDB while active queries are still running could lead to a crash due to premature release of the CURSOR (MOD-10681).
• #6418 Errors when loading schema from RDB get incorrectly cleared (MOD-10307).
• #6405 Validate compatibility against RedisJSON version upon open key (MOD-10298).

Improvements:

• #6466 Handle excessive error logs when handling JSON.DEL errors (MOD-10266).
• #6663 Time measurement on FT.PROFILE using thread-independent clock mechanism (MOD-10622).
• #6646 Response on RESP2/3 validation was inefficiently consuming excessive CPU cycles (MOD-9687).

v2.8.28 (June 2025)

This is a maintenance release for RediSearch 2.8.

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

Bug fixes:

• #6207 Continuous increasing of index error counts on FT.INFO could lead to an overflow and memory leak (MOD-9396).
• #6349 Search on terms larger than 128 characters could lead to missing matches (MOD-6786).
• #6305 While iterating over a large index, frequent document updates could hit the TIMEOUT, causing a crash (MOD-9856).

Improvements:

• #6340 Added a locking mechanism for collecting FT.INFO statistics when concurrently running the index sanitiser (MOD-10007, MOD-9761).

v2.8.27 (May 2025)

This is a maintenance release for RediSearch 2.8.

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

Bug fixes:

• #6191 Reindexing from RDB with multiple vector indices could lead to a crash due to cluster health check - NodeWD (MOD-9220,MOD-8809)
• #6031 FT.CURSOR...DEL while another thread is reading it could lead to a crash (MOD-9408,MOD-9432,MOD-9433,MOD-9434,MOD-9435)
• #5966 Indexing documents using TEXT without the text in the documents leads to an inf or nan score (MOD-9423)
• #6057 Avoid lazy expiration in background indexing for Active-Active setup, preventing keys from expiring incorrectly (MOD-9486)
• #6113 A timeout failure is returned when the ON_TIMEOUT RETURN policy is set to stop the collection of partial results - best effort (MOD-9612)

Improvements:

• #6008 Parser for intersections on parentheses and sub-queries order won't affect full-text scores (MOD-9278)

v2.8.26 (April 2025)

This is a maintenance release for RediSearch 2.8.

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

Bug fixes:

• #5864 Last query result using FT.AGGREGATE with ON_TIMEOUT RETURN and using multi-threading could be missing (MOD-9222)
• #5863 Collecting empty results from shards during FT.AGGREGATE with RESP3 could cause a crash (MOD-9174)

Improvements:

• #5938 Improved performance (reduced CPU time) of collecting vector index statistics(MOD-9354)
• #5800 Improved accuracy of index memory reporting by correcting a bug that caused negative memory counts (MOD-5904)

Created on: 2025-04-21T14:51:40Z

v2.8.25 (March 2025)

This is a maintenance release for RediSearch 2.8.

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

Bug fixes:

• #5709 Weights in the query string are ignored if using SCORER BM25 (MOD-7896)
• #5788 Cursor with SORTBY is never depleted, blocking queries if the cursor limit is reached (MOD-8483)
• #5788 Empty results with RESP3 due to the TIMEOUT, even if ON_TIMEOUT is set to RETURN(MOD-8482)
• #5788 Cursor with RESP3 on FT.AGGREGATE is never depleted, blocking queries if cursor the limit is achieved (MOD-8515)
• #5788 Using FT.CURSOR READ on queries that timed out led to fewer results than expected (MOD-8606)
• #5810 The total_results field of the FT.AGGREGATE command is not correct in RESP3 (MOD-9054)

Improvements:

• #5788 Corrected a coordinator race condition that prevented premature release, avoiding errors and inconsistencies during query executions (MOD-8794)

v2.8.24 (February 2025)

This is a maintenance release for RediSearch 2.8.

Update urgency: LOW No need to upgrade unless there are new features you want to use.

Bug fixes:

• #5647 FT.SEARCH using Cyrillic characters and wildcards delivering no results (MOD-7944)

v2.8.23 (February 2025)

This is a maintenance release for RediSearch 2.8.

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

Bug fixes:

• #5605 Changes on the memory block reading logic could cause crash on FT.SEARCH with error "Redis 7.4.2 crashed by signal: 11, si_code: 128"

Known limitations:

• Only the first 128 characters of string fields are normalized to lowercase during ingestion (for example, on HSET). Example:

  HSET doc __score 1.0 name "idx1S...S" mynum 1          # Assume "S...S" is a string of 252 capital S's
  FT.CREATE "idx" SCHEMA "name" "TEXT" "mynum" "NUMERIC"
  FT.SEARCH "idx" "@name:idx1S...S"                      # Assume "S...S" is a string of 252 capital S's
  

  The FT.SEARCH command will return no documents.

v2.8.22 (January 2025)

This is a maintenance release for RediSearch 2.8.

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

Bug fixes:

• #5475 NOSTEM option does not work on query, just tokenising (MOD-7634)
• #5542 Querying for the latest document added to the index may result in a crash if the last block is not read (MOD-8561).

v2.8.21 (January 2025)

This is a maintenance release for RediSearch 2.8.

Update urgency: SECURITY: There are security fixes in the release.

Security and privacy:

• #5457 (CVE-2024-51737) Query: potential out-of-bounds write (MOD-8486)

Bug fixes:

• #5299 Prefix/Infix/Suffix queries longer than 1024 chars could cause a crash (MOD-7882)
• #5303 Expired keys while background indexing could cause cross slot error when using replicaof (MOD-7949)
• #5280 FT.CURSOR READ retrieving deleted TAG fields cause a crash (MOD-8011)
• #5427 FT.AGGREGATE on numeric fields lead to failed_calls count increase on clustered DBs (MOD-8058)
• #5242 Memory count on bytes_collected by the index sanitiser with missing values (MOD-8097, MOD-8114)
• #5167 Cursors from queries that timed out weren't depleted causing exhaustion of number of cursors available(MOD-8009)

Improvements:

• #5260 Optimizing index consumed memory with the creation only upon write operations (MOD-8125)

v2.8.17 (August 2024)

This is a maintenance release for RediSearch 2.8.

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

• Bug fixes:

  • #4941 Adjusting the module configuration to avoid routing overload on the first shard in a clustered database (MOD-7505)
  • #4950 FT.PROFILE on AGGREGATE numeric queries could cause a crash due to reusing internal CURSOR in large range of numeric values (MOD-7454)

v2.8.16 (August 2024)

This is a maintenance release for RediSearch 2.8.

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

• Bug fixes:

  • #4896 - FT.AGGREGATE with VERBATIM option is not handled by the shards in cluster mode (MOD-7463)
  • #4917 - Union query, similar to "is|the", starting with 2 stopwords could cause a crash (MOD-7495)
  • #4921 - Counting twice the field statistics at the #search section of an INFO response (MOD-7339)
  • #4939 - Query warning when using RESP3 response for reaching MAXPREFIXEXPANSION (MOD-7588)
  • #4930 - Loop when using the wildcard w'term' and prefix/infix/suffix pattern 'ter*' leading shard to restart (MOD-7453)
  • #4912 - Avoid stemming expansion when querying for numeric values (MOD-7025)

v2.8.15 (July 2024)

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

• Bug fixes:

  • #4754 - Correct return the maximum value for negative values when using MAX reducer (MOD-7252)
  • #4737 - Separators ignored when escaping backslash \ after the escaped character such as in hello\\,world ignoring , (MOD-7240)
  • #4717 - Sorting by multiple fields SORTBY 2 @field1 @field2 was ignoring the subsequent field(MOD-7206)
  • #4803 - Keys expiring during query returning empty array (MOD-7010)
  • #4794 - Index sanitiser (GC) trying to clean deleted numeric index could cause a crash (MOD-7303)

• Improvements:

  • #4792 - Add character validations to simple string replies and escape it when required(MOD-7258)
  • #4768 - Indicate which value is missing on the error message at the aggregation pipeline (MOD-7201)
  • #4745 - GROUPBY recursion cleanup (MOD-7245)
  • #4823 - Mechanism of keys expiration during the query execution clearing intermediate results

v2.8.14 (June 2024)

This is a maintenance release for RediSearch 2.8.

Update urgency: MODERATE: Program an upgrade of the server, but it's not urgent.

• Bug fixes:

  • #4614 Shards become unresponsive when using FT.AGGREGATE with APPLY 'split(...)'(MOD-6759)
  • #4556 FT.EXPLAIN returns additional } when querying using wildcards (MOD-6768)
  • #4646 FT.DROPINDEX with DD flag deleted keys in one AA cluster but not the others (MOD-1855)

• Improvements:

  • #4595 Report memory of the TAG and TEXT tries (MOD-5902)
  • #4669 Inverted index memory counting (MOD-5977,MOD-5866)
  • #4687 Add missing FT.INFO fields when used within a cluster (MOD-6920)

v2.8.13 (March 2024)

This is a maintenance release for RediSearch 2.8.

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

Details:

• Bug fixes:

  • #4481 Query syntax on GEOSHAPE accepting just prefix instead of complete predicate (MOD-6663)
  • #4513 FT.CURSOR READ in a numeric query causing a crash (MOD-6597)
  • #4534 FT.PROFILE with incorrect arguments could cause a crash on cluster setup (MOD-6791)
  • #4530 Some parameter settings using just prefixes instead of full values were working (MOD-6709)
  • #4539 Unfree memory while re-indexing a new RDB as it's loading could cause a crash (MOD-6831, 6810)
  • #4498 Vector pre-filtered query (hybrid query) that times out causing a crash due to deadlock when trying to write a new document (MOD-6510, MOD-6244)
  • #4495 FT.SEARCH accessing an inexistent memory address causes a crash if using the deprecated FT.ADD command (MOD-6599)

• Improvements:

  • #4502 Handle error properly when trying to execute Search commands on cluster setup as part of MULTI ... EXEC or LUA script (MOD-6541)
  • #4526 Adding detailed geometry info on error messages (MOD-6701)

v2.8.12 (March 2024)

This is a maintenance release for RediSearch 2.8.

Update urgency: MODERATE: Program an upgrade of the server, but it's not urgent.

Details:

• Bug fixes:

  • #4476 Split INFIX and SUFFIX report on FT.EXPLAIN and FT.EXPLAINCLI (MOD-6186)
  • #4467 Memory leak upon suffix query for a TAG indexed with WITHSUFFIXTRIE (MOD-6644)
  • #4403 Clustered FT.SEARCH hangs forever without replying when an invalid topology is found (MOD-6557)
  • #4355 Searching for a synonym will iterate in the same group multiple times, causing a performance hit (MOD-6490)

• Improvements:

  • #4313 Memory allocation patterns on the memory used to query GEOSHAPE types (MOD-6431)

v2.8.11 (January 2024)

This is a maintenance release for RediSearch 2.8.

Update urgency: MODERATE: Program an upgrade of the server, but it's not urgent.

Details:

• Bug fixes:

  • #4324 Internal cluster mechanism not waiting until all replies from shards causing a crash (MOD-6287)
  • #4297 Execution loader when using FT.AGGREGATE with LOAD stage failing to buffer the right results potentially causing a crash (MOD-6385)

• Improvements:

  • #4264 Granularity of the time reporting counters on FT.PROFILE (MOD-6002)

v2.8.10 (January 2024)

This is a maintenance release for RediSearch 2.8.

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

Details:

• Bug fixes:

  • #4287 Re-index process while syncing from the replica causes a crash due to internal index variable initialization (MOD-6337, MOD-6336)
  • #4249 Memory tracking on cluster setups causing high memory usage and potentially Out-of-Memory (MOD-6123, MOD-5639)
  • #4244 Profiling FT.AGGREGATE using the WITHCURSOR flag with a - clause causes a crash due to timeout (MOD-5512)
  • #3916 Expiring JSON documents while querying it causing a crash due to deadlock (MOD-5769, MOD-5895, MOD-6189, MOD-5895)
  • #4235 Memory excessively growing on databases caused by unbalanced nodes on inverted index trie (MOD-5880, MOD-5952, MOD-6003)
  • #4190 Profiling FT.AGGREGATE causes a crash on RESP3 replies (MOD-6250, MOD-6295)
  • #4148, #4038 ON_TIMEOUT FAIL\RETURN policies in the cluster setup not being respected (MOD-6035, MOD-5948, MOD-6090)
  • #4110 Format of error response contains inconsistencies when timing out (MOD-6011, MOD-5965)
  • #4104 FT.SEARCH not responding when using TLS encryption on Amazon Linux 2 (MOD-6012)
  • #4009 In cluster setup does not return a timeout error for FT.SEARCH (MOD-5911)
  • #3920 In cluster setup does not return a timeout error for FT.AGGREGATE (MOD-5209)
  • #3914 FT.CURSOR READ with geo queries causing a crash when data is updated between the cursor reads (MOD-5646)
  • #4220 Server crash when attempting to run the ForkGC (Garbage Collection routine) after dropping the index (MOD-6276)

• Improvements:

  • #3682 Report last key error and field type indexing failures on FT.INFO (MOD-5364)
  • #4236 Adding Vector index parameters at the FT.INFO report (MOD-6198)
  • #4196 Check for timeout after results processing in FT.SEARCH on cluster setup (MOD-6278)
  • #4164 Report TIMEOUT, MAXPREFIXEXPANSION warnings in RESP3 replies (MOD-6234)
  • #4165 Indicate timeout on FT.PROFILE report (MOD-6184)
  • #4149 Indicate timeout from Cursor on FAIL timeout policy (MOD-5990)
  • #4147 Initialization of the maximum numeric value range leading to a better balance of the index leaf splitting (MOD-6232)
  • #3940 Query optimization when predicate contains multiple INTERSECTION (AND) of UNION (OR) (MOD-5910)
  • #4059 Return cursor id when experiencing a timeout, when the policy is ON_TIMEOUT RETURN (MOD-5966)
  • #4006 Possibly problematic index name alias validation (MOD-5945)

v2.8.9 (October 2023)

This is a maintenance release for RediSearch 2.8.

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

Details:

• Bug fixes:

  • #3874 Heavy document updates causing memory growth once memory blocks weren't properly released (MOD-5181)
  • #3967 Resharding optimizations causing the process to get stuck (MOD-5874, MOD-5864)
  • #3892 After cleaning the index the GC could cause corruption on unique values (MOD-5815)
  • #3853 Queries with WITHCURSOR making memory growth since CURSOR wasn't invalidated in the shards (MOD-5580)

• Improvements:

  • #3938 Propagating error messages in multiple shards database, instead of failing silently (MOD-5211)
  • #3903 Added support for Rocky Linux 9 and RHEL9 (MOD-5759)

v2.8.8 (September 2023)

This is a maintenance release for RediSearch 2.8.

Update urgency: SECURITY: There are security fixes in the release.

Details:

• Security and privacy:

  • #3788 Don’t expose internal cluster commands (MOD-5706)
  • #3844 Limits maximum phonetic length avoiding to be exploit (MOD 5767)

• Bug fixes:

  • #3771 Broken lower() and upper() functions on APPLY stage in FT.AGGREGATE in DIALECT 3 (MOD-5041)
  • #3752 Setting low MAXIDLE parameter value in FT.AGGREGATE cause a crash (MOD-5608)
  • #3780 Wrong document length calculation causing incorrect score values (MOD-5622)
  • #3808 LOAD step after a FILTER step could cause a crash on FT.AGGREGATE (MOD-5267)
  • #3823 APPLY or FILTER parser leak (MOD-5751)
  • #3837 Connection using TLS fail on Redis 7.2 (MOD-5768)
  • #3856 Adding new nodes to OSS cluster causing a crash (MOD-5778)
  • #3854 Vector range query could cause Out-of-Memory due to a memory corruption (MOD-5791)

• Improvements:

  • #3534 Vector Similarity 0.7.1 (MOD-5624)

v2.8 GA (v2.8.4) (July 2023)

This is the General Availability release of RediSearch 2.8.

Headlines

RediSearch 2.8 introduces support for RESP3, new features, performance improvements, and bug fixes.

What's new in 2.8.4

This new major version introduces new and frequently asked for Geo Polygon Search, adding the GEOSHAPE field type that supports polygon shapes using WKT notation. Besides the current GEO (alias for GEOPOINT) used in geo range queries, we add support for POLYGON and POINT as new geo shape formats (new GEOSHAPE). In addition, 2.8 brings performance improvements for SORT BY operations using FT.SEARCH and FT.AGGREGATE, and new FORMAT for enhanced responses on FT.SEARCH and FT.AGGREGATE in RESP3 only.

Features:

• Introduce support for geo polygon shapes and queries:

  • Adding GEOSHAPE field type to map polygons in the SCHEMA on FT.CREATE (MOD-4798)

  • Support for polygons POLYGON and POINT using WKT notation, for example POLYGON((lon1 lat1, lon2 lat2, ...))

  • Adjust the query syntax on FT.SEARCH for polygons using the predicate @geom:[OPERATOR $poly] and defining polygon in WKT format as PARAMS 2 poly "POLYGON((10 20, ...))" using DIALECT 3

  • Initially WITHIN and CONTAINS operators with GEOSHAPES for now

  • Support multiple coordinate systems: cartesian (X,Y) with the flag FLAT for flat earth and geographic (lon, lat) using the flag SPHERICAL (MOD-5303). Geographic coordinate system using spherical indexing as default (SPHERICAL)

  • Add memory usage per Geometry Index in the FT.INFO response report (MOD-5278)

• Introduce performance optimization for sorting operations on FT.SEARCH and FT.AGGREGATE as default on DIALECT 4. It will improve performance in 4 different scenarios, listed below:

  • Skip Sorter - applied when there is no sort of any kind. The query can return once it reaches the LIMIT requested results.

  • Partial Range - applied when there is a SORTBY a numeric field, with no filter or filter by the same numeric field, the query iterates on a range large enough to satisfy the LIMIT requested results.

  • Hybrid - applied when there is a SORTBY a numeric field in addition to another non-numeric filter. Some results will get filtered, and the initial range may not be large enough. The iterator then is rewinded with the following ranges, and an additional iteration takes place to collect LIMIT requested results.

  • No optimization - If there is a sort by score or by non-numeric field, there is no other option but to retrieve all results and compare their values.

• Add WITHCOUNT argument that allow return accurate counts for the query results with sorting. This operation processes all results in order to get accurate count, being less performant than the optimized option (default behavior on DIALECT 4) (MOD-5311)

• New FORMAT argument in FT.SEARCH and FT.AGGREGATE to retrieve the results as JSON strings or RESP3 hierarchical structures (RESP3 only) (MOD-5390)

Improvements (since 2.8.3):

• #3717 - Polygon shapes validation and orientation correction when clockwise (MOD-5575)

• #3534 - Vector Similarity [0.7.0]

• #3657 - Allow GC calls for all tiered indexes in the schema

• #3701 - HNSW is now using data blocks to store vectors and metadata instead of array

Changed behavior:

• #3355, #3635 Expired keys deleted from replica's index, returning an empty array instead of nil (MOD-4739)