v2.6.18

This is a maintenance release for RediSearch 2.6

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

Details

Bug fixes:
#4557 Additional "}" on wildcards replies for FT.EXPLAIN (MOD-6768)

v2.8.13

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 loading a new RDB could cause a crash (MOD-6831, 6810)
• #4498 Vector pre-filtered query (hybrid query) that timeout 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.6.17

This is a maintenance release for RediSearch 2.6

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

Details

Bug fixes:

• #4524 FT.CURSOR READ in a numeric query causing a crash (MOD-6597)
• #4543 FT.SEARCH accessing an inexistent memory address causes a crash if using deprecated FT.ADD command (MOD-6599)
• #4535 FT.PROFILE with incorrect arguments could cause a crash on cluster setup (MOD-6791)
• #4540 Unfree memory from an existing RDB while re-indexing loading a new RDB could cause a crash (MOD-6831, 6810)
• #4485 Some parameter settings using just prefixes instead of full values were working (MOD-6709)

Improvements:

• #4502 Handle error properly when trying to execute Search commands on cluster setup as part of MULTI/EXEC or LUA script (MOD-6541)

v2.8.12

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.6.16

This is a maintenance release for RediSearch 2.6

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

Details

Bug fixes:

• #4477 Split INFIX and SUFFIX report on FT.EXPLAIN and FT.EXPLAINCLI (MOD-6186)
• #4468 Memory leak upon suffix query for a TAG indexed with WITHSUFFIXTRIE (MOD-6644)
• #4407 Clustered FT.SEARCH hangs forever without replying when an invalid topology is found (MOD-6557)
• #4359 Searching for a synonym will iterate in the same group multiple times, causing a performance hit (MOD-6490)
• #4310 Memory tracking on cluster setups causing high memory usage and potentially Out-of-Memory (MOD-6123, MOD-5639)

v2.8.11

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

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.6.15

This is a maintenance release for RediSearch 2.6

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

Details

Bug fixes:

• #4244, #4255 Profiling FT.AGGREGATE using the WITHCURSOR flag causes a crash due to timeout (MOD-5512)
• #4238 Memory excessively growing on databases caused by unbalanced nodes on inverted index trie (MOD-5880, MOD-5952, MOD-6003)
• #3995 FT.CURSOR READ with geo queries causing a crash when data is updated between the cursor reads (MOD-5646)
• #4155 FT.SEARCH not responding when using TLS encryption on Amazon Linux 2 (MOD-6012)

Improvements:

• #4176 Initialization of the maximum numeric value range leading to a better balance of the index leaf splitting (MOD-6232)
• #4123 Possibly problematic index name alias check-in command multiplexing (MOD-5945)
• #4195 Query optimization when predicate contains multiple INTERSECTION (AND) of UNION (OR) (MOD-5910)

v2.6.14

This is a maintenance release for RediSearch 2.6

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

Details

Bug fixes:

• #3783 Broken lower and upper APPLY functions in FT.AGGREGATE on DIALECT 3 (MOD-5041)
• #3823 APPLY or FILTER expression causing a leak (MOD-5751)
• #3899 Connection using TLS fail on Redis (MOD-5768)
• #3910 Heavy document updates causing memory growth if memory blocks weren't properly released (MOD-5181)(MOD-5757)
• #3928 Queries with WITHCURSOR making memory growth since CURSOR wasn't invalidated in the shards (MOD-5580)
• #3946 Vector range query could cause Out-of-Memory due to memory corruption (MOD-5791)
• #3972 Adding new nodes to OSS cluster can cause a crash (MOD-5778)
• #3957 After cleaning the index, the index sanitizer (GC) could corrupt on unique values (MOD-5815)
• #4002 Setting a low MAXIDLE parameter value in FT.AGGREGATE causes a crash (MOD-5608)

Security and privacy:

• #3844 Limits maximum phonetic length to avoid vulnerability (MOD 5767)

v2.8.9

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 if 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 corrupt 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)