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

• #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 a large range of numeric values (MOD-7454)

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.

Details

This update aligns the minimal version number requirements for RediSearch with Redis Enterprise

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

This update aligns the minimal version number requirements for RediSearch with Redis Enterprise

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 reusing internal CURSOR in large range of numeric values (MOD-7454)

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:

• #4944 Adjusting the module configuration to avoid routing overload on the first shard in a clustered database (MOD-7505)
• #4897 FT.AGGREGATE with VERBATIM option is not handled by the shards in cluster mode (MOD-7463)
• #4918 Union query, similar to "is|the", starting with 2 stopwords could cause a crash (MOD-7495)
• #4919 Counting twice the field statistics at #search section of INFO response (MOD-7339)
• #4923 Loop when using the wildcard w'term' and preffix/infix/suffix pattern 'ter*' leading shard to restart (MOD-7453)
• #4954 FT.PROFILE on AGGREGATE numeric queries could cause a crash due reusing internal CURSOR in large range of numeric values (MOD-7454)

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 #search section of 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 preffix/infix/suffix pattern 'ter*' leading shard to restart (MOD-7453)
• #4912 Avoid stemming expansion when querying for numeric values (MOD-7025)

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:

• #4916 Union query, similar to "is|the", starting with 2 stopwords could cause a crash (MOD-7495)
• #4895 FT.AGGREGATE with VERBATIM option is not handled by the shards in cluster mode (MOD-7463)
• #4922 Counting twice the field statistics at #search section of INFO response (MOD-7339)

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:

• #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

This is a maintenance release for RediSearch 2.6

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

Bug fixes:

• #4755 Correct return the maximum value for negative values when using MAX reducer (MOD-7252)
• #4733 Separators ignored when escaping backslash \ after the escaped character such as in hello\\,world ignoring , (MOD-7240)
• #4717 Sorting by multiple fields as in SORTBY 2 @field1 @field2 was ignoring the subsequent field (MOD-7206)

Improvements:

• #4793 Add character validations to simple string replies and escape it when required(MOD-7258)
• #4769 Indicate which value is missing on the error message at the aggregation pipeline (MOD-7201)
• #4746 GROUPBY recursion cleanup (MOD-7245)

This is the General Availability release of RediSearch 2.10

Headlines:

This latest RediSearch introduces memory-efficient vector data types, enhanced indexing capabilities with support to empty and missing fields, simplified query syntax, and expanded geospatial search features

What's new in 2.10.5

This new major version introduces new BFLOAT16 and FLOAT16 vector data types, reducing memory consumed by vectors while preserving accuracy. This update also includes highly requested support for indexing empty and missing values and enhances the developer experience for queries with exact matching capabilities. Developers can now match TAG fields without needing to escape special characters, making the onboarding process and use of the query syntax simpler. Lastly, Geospatial search capabilities have been expanded with new INTERSECT and DISJOINT operators, a new way to expose and apply full-text scores in the aggregation pipeline as custom function and ergonomics have been improved by providing better reporting of the memory consumed by the index.

Features:

• Enhancing exact matching queries with TAG avoiding escaping special meaning characters using the simpler syntax '@tag:{"my-query%term"}' and NUMERIC queries:

  • #4802 Using double quotes to wrap you exact matching query terms such as @email:{"test@redis.com"} in DIALECT 2( MOD-7299)
  • #4676, #4433 Enhancing query parser to avoid unnecessary escaping (MOD-5756)
  • #4527 Enhancing exact matching queries for NUMERIC using single value FT.SEARCH idx @numeric:[3456] (MOD-6623)
  • #4802 Enabling support to single operators for NUMERIC queries such as equivalence ==, difference !=, greater than > and >= and less than < and <= as in FT.SEARCH idx '@numeric==3456' (MOD-6749)

• Adding new keywords to support indexing empty values using INDEXEMPTY and missing values using INDEXMISSING per field in the SCHEMA while defining the index with FT.CREATE

  • #4663, #4721 Indexing empty strings values "" for TAG and TEXT fields (MOD-6540, MOD-7200)
  • #4721 Updating the query parser to support empty values query for TEXT as FT.SEARCH idx '@text_field:""'or FT.SEARCH idx '""' and for TAG as in FT.SEARCH idx '@tag_field:{""}' (MOD-7200)
  • #4720, #4635 Indexing missing values for all field types introducing the query syntax function ismissing(@field) enabling query for missing fields as in FT.SEARCH idx 'ismissing(@text)' (MOD-6532)

• Enabling new vector data types reducing memory consumed by vectors with the new BFLOAT16 and FLOAT16

  • #4674 Adding support BFLOAT16 and FLOAT16 in the vector index definition (MOD-6765, MOD-6776)

• Exposing the full-text score values during the aggregation pipeline using ADDSCORES. When calling the scores you can use @__score in the pipeline as in FT.AGGREGATE idx 'hello' ADDSCORES SORTBY 2 @__score DESC

  • #4859 Expose scores to FT.AGGREGATE pipeline (MOD-7190)

• #4227 Adding support for new operators INTERSECT and DISJOINT when querying for GEOSHAPE polygons (MOD-6178)

Bug fixes (since 2.10.4):

• #4854 Avoid expansion on stemming from numeric values (MOD-7025)

Improvements (since 2.10.4):

• #4865 Add coverage for cleaning garbage entries at indexing missing fields (MOD-7415)

Notes:

• 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 GA flag.
• Minimal Redis version: 7.4
• If indexing and querying RedisJSON data structures, this version is best combined with RedisJSON 2.8 (v2.8.3 onwards)