Skip to content

Releases: RediSearch/RediSearch

v2.10.15

24 Mar 18:47
b8506c5
Compare
Choose a tag to compare

This is a maintenance release for RediSearch 2.10

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

Bug fixes:

  • #5734 Cursor with SORTBY is never depleted blocking queries if cursor limit is achieved (MOD-8483)
  • #5734 Empty results with RESP3 due to the TIMEOUT even if setting to deliver partial results - ON_TIMEOUT policy (MOD-8482)
  • #5734 Cursor with RESP3 on FT.AGGREGATE is never depleted blocking queries if cursor limit is achieved (MOD-8515)
  • #5734 Using FT.CURSOR READ on queries that timed out led to fewer results than expected (MOD-8606)
  • #5804 FT.AGGREGATEresponse in RESP3 the total_results field is not correct (MOD-9054)

Improvements:

  • #5734 Coordinator race condition preventing the premature release and avoiding errors and inconsistencies during query executions (MOD-8794)

v2.8.25

24 Mar 18:55
7ece970
Compare
Choose a tag to compare

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 is ignored if using SCORER BM25 (MOD-7896)
  • #5788 Cursor with SORTBY is never depleted blocking queries if cursor limit is achieved (MOD-8483)
  • #5788 Empty results with RESP3 due to the TIMEOUT even if setting to deliver partial results - ON_TIMEOUT policy (MOD-8482)
  • #5788 Cursor with RESP3 on FT.AGGREGATE is never depleted blocking queries if cursor limit is achieved (MOD-8515)
  • #5788 Using FT.CURSOR READ on queries that timed out led to fewer results than expected (MOD-8606)
  • #5810 FT.AGGREGATEresponse in RESP3 the total_results field is not correct (MOD-9054)

Improvements:

  • #5788 Coordinator race condition preventing the premature release and avoiding errors and inconsistencies during query executions (MOD-8794)

v2.6.28

25 Mar 10:32
a19d287
Compare
Choose a tag to compare

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.

Bug fixes:

  • #5712 Weights in the query string are ignored if using SCORER BM25 (MOD-7896)

v2.10.14

17 Mar 09:53
3d3e505
Compare
Choose a tag to compare

This is a maintenance release for RediSearch 2.10

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

Bug fixes:

  • #5704 Weights in the query string is ignored if using SCORER BM25 (MOD-7896)

v2.8.24

25 Feb 13:11
3fb2635
Compare
Choose a tag to compare

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 deliverying no results (MOD-7944)

v2.6.27

25 Feb 13:14
e753767
Compare
Choose a tag to compare

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.

Bug fixes:

  • #5648 FT.SEARCH using cyrillic characters and wildcards deliverying no results (MOD-7944)

v2.10.13

25 Feb 13:09
3053af3
Compare
Choose a tag to compare

This is a maintenance release for RediSearch 2.10

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

Bug fixes:

  • #5646 FT.SEARCH using cyrillic characters and wildcards deliverying no results (MOD-7944)
  • #5163 SCORER selection ignored on FT.AGGREGATE commands in clustered database

v2.8.23

07 Feb 09:54
Compare
Choose a tag to compare

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 crashed by signal: 11, si_code: 128"

v2.10.12

07 Feb 10:00
Compare
Choose a tag to compare

This is a maintenance release for RediSearch 2.10

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

Bug fixes:

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

v2.6.26

07 Feb 09:56
Compare
Choose a tag to compare

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!

Bug fixes:

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