2.6 GA (v2.6.3)

This is the General Availability release of RediSearch 2.6.

Highlights

This new major version introduces the ability to search using wildcard queries for TEXT and TAG fields. This enables the frequently asked feature of suffix search (*vatore and ant?rez are now supported).
In addition, the 2.6 release is all about multi-value indexing and querying of attributes for any attribute type ( Text, Tag, Numeric, Geo and Vector) defined by a JSONPath leading to an array or to multiple scalar values.
Lastly, this version adds support for indexing double-precision floating-point vectors and range queries from a given vector.

Details

Improvements:

• #2886 Support for wildcard queries for TEXT and TAG fields, where
  • ? matches any single character
  • * matches zero or more characters
  • use ' and \ for escaping, other special characters are ignored
  • #2932 Optimized wildcard query support (i.e., suffix trie)
• Multi-value indexing and querying
  • #2819, #2947 Multi-value text search - perform full-text search on array of string or on a JSONPath leading to multiple strings
  • #3131 Geo #3118 Vector #2985 Numeric #3180 Tag
  • #3060 Return JSON rather than scalars from multi-value attributes. This is enabled via Dialect 3 in order not to break existing applications.
  • Support indexing and querying of multi-value JSONPath attributes and/or arrays (requires JSON >2.4.1)
  • #3182 Support for SORTABLE fields on JSON in an implicit un-normalized form (UNF)
• #3156 Vector similarity 0.5.1:
  • Better space optimization selection (#175)
  • Aligning index capacity with block size (#177)
  • #3129 Support FLOAT64 as vector data type
  • #3176 Range query support
  • #3105 Support query attributes for vector queries

Bugs (since 2.6-RC1 / v2.6.1):

• #3197 Failure to create temporary indices
• #3098 Wrong return value in Geo query
• #3230 Use the correct total number of matching records

Notes:

• The version inside Redis will be 2.6.3 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag.
• Minimal Redis version: 6.0
• With this release, we stop supporting direct upgrades from RediSearch v1.4 and v1.6 that are End-of-Life. Such rdb files can still be upgraded to RediSearch 2.0 first
• If indexing and querying RedisJSON data structures, this version is best combined with RedisJSON 2.4 GA (v2.4.1 onwards)
• License update: see LICENSE.txt

v2.4.16

This is a maintenance release for RediSearch 2.4

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

Details

Bug fixes:

• #2962 Crash upon AOF preload - Use local GC context in periodic callback (MOD-3951)
• #2863 High CPU Utilization - Change MAX_LEV_DISTANCE to 4 (MOD-3563)
• #3041, #3063, #3051, #3143 Several memory leaks (MOD-4121, MOD-4252)
• #3119 Crash on intersect iterator GetCriteriaTester (MOD-4200)
• #3128 Filter rules must be reevaluated per index per document (MOD-4207)
• #3127 Fix assertion failure on wrong result counting, which leads to a crash (MOD-4214)
• #3171 Missing implementation of NumericRangeIterator_OnReopen which lead to crash (MOD-4255)
• #3191 Wrong query iterator casting which resulted in 100% CPU utilization (MOD-4290)
• #3197 Release failed to create temporary indices on the main thread (MOD-4388)
• #2981 Double freeing in iterators of hybrid queries resulting in crash (MOD-4411)
• #3161 Latency used to increase over time when combining INKEYS and wildcard query (MOD-4343)

2.6-RC1 (v2.6.1)

This is the first Release Candidate of RediSearch 2.6.

Highlights

This new major version introduces the ability to search using wildcard queries for TEXT and TAG fields. This enables the frequently asked feature of suffix search (*vatore and ant?rez are now supported).
In addition, the 2.6 release is all about multi-value indexing and querying of attributes for any attribute type ( Text, Tag, Numeric, Geo and Vector) defined by a JSONPath leading to an array.
Lastly, this version adds support for indexing double-precision floating-point vectors and range queries from a given vector.

Details

Improvements:

• #2886 Support for wildcard queries for TEXT and TAG fields, where
  • ? matches any single character
  • * matches zero or more characters
  • use ’ and \ for escaping, other special characters are ignored
  • #2932 Optimized wildcard query support (i.e., suffix trie)
• Multi-value indexing and querying
  • #2819, #2947 Multi-value text search - perform full-text search on array of string or on a JSONPath leading to multiple strings
  • #3131 Geo #3118 Vector #2985 Numeric #3180 Tag
  • #3060 Return JSON rather than scalars from multi-value attributes. This is enabled via Dialect 3 in order not to break existing applications.
  • #3182 Support for SORTABLE fields on JSON in an implicit un-normalized form (UNF)
• #3156 Vector similarity 0.5.1:
  • Better space optimization selection (#175)
  • Aligning index capacity with block size (#177)
  • #3129 Support FLOAT64 as vector data type
  • #3176 Range query support
  • #3105 Support query attributes for vector queries

Notes:

• The version inside Redis will be 2.6.1 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a Release Candidate flag. The GA version will follow soon.
• Minimal Redis version: 6.0

v2.4.15

This is a maintenance release for RediSearch 2.4

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

Details

Bug fixes:

• #3095 Replace order of parsing the parameters and query in the coordinator (MOD-4205)
• #3012 Improved efficiency of LLAPI findInfo which could reduce stability during upgrade in Redis Enterprise (MOD-4197, MOD-4052)
• #3040, #3049 fix for SORTBY numeric field for non-SORTABLE fields on the coordinator (MOD-4115)
• #3050 Results from fields from a missing value should come last when combined with SORTBY. (MOD-4120 )

Improvements:

• #3047 Add strlen string function to FT.AGGREGATE (MOD-4141)
• #3038 Add number_of_uses to FT.INFO for the number of times the index was queried

2.6-M01 (v.2.6.0)

This is the first Milestone of RediSearch 2.6.

Highlights

This first milestone release introduces the ability to search using wildcard queries for TEXT and TAG fields. This enables the frequently asked feature of suffix search.
In addition, the 2.6 release is all about multi-value indexing and querying of attributes defined by a JSONPath leading to an array. In this first milestone release, we add support for full-text search indexing and querying multi-value string attributes.
In upcoming milestone releases, we'll add multi-value indexing support for numeric and geo attribute types.

Details

Improvements:

• #2886 Support for wildcard queries for TEXT and TAG fields, where
  • ? matches any single character
  • * matches zero or more characters
  • use ’ and \ for escaping, other special characters are ignored
• #2932 Optimized wildcard query support (i.e., suffix trie)
• #2819, #2947 Multi-value text search - perform full text search on array of string or on a JSONPath leading to multiple strings
• #2953 Vector similarity 0.4.2:
  • Better space optimization selection (#175)
  • Aligning index capacity with block size (#177)

Performance improvements:

• #2958 Only scan modified indexes
• #2906 Optimization for sorting an intersect iterator's children iterators

Bugs:

• #3017 Redis crashes on a new doc Numeric index [MOD-4057]
• #2950, #2952, #2965 Avoid terms dictionary rehashing on multiple readers
• #2865 Endless loop on negative radius search

v2.4.14

This is a maintenance release for RediSearch 2.4

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

Details

Improvements:

• Vector similarity v0.3.2
• #2955 Add timeout during prefix query (MOD-3949)
• #2957 Efficient removal from prefix-list for cases with many indices
• #2760, #2916 Expose Index statistics information in INFO MODULES section [MOD-2611]

Bugs:

• #2937 Returning NULL response after encountering an expired document (MOD-3515)
• #2962 Crash in multiple shards deployment when updating/changing the index - GC routine (MOD-3951)
• #2986 Memory leak related to schema prefixes
• #2967 Bug in the intersect iterator
• #2900 Disable SORTBY + MAX in FT.SEARCH which could cause crash (but was not supported) [MOD-3540]

v2.4.11

This is a maintenance release for RediSearch 2.4

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

Details

Bug fixes:

• #2892 Combining SORTBY with MAX on FT.SEARCH (which is not supported) caused an inconsistent response and out-of-memory (MOD-3540, MOD-3644)
• VecSim v0.3.1
  • HNSW indices: reclaim memory upon deletion - HNSW index's data structures now reclaim memory and shrink upon deletion

Improvements:

• VecSim v0.3.1
  • HNSW indices: delete procedure is up to 40% faster
  • More accurate memory consumption reporting for HNSW indices

v2.4.10

This is a maintenance release for RediSearch 2.4

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

Details

Bug fixes:

• #2863 Crash due to too high (Levenstein) DISTANCE in FT.SPELLCHECK. This fix limits the DISTANCE to 4. (MOD-3563)
• #2875 Not all documents with Vector fields were indexed with Redis-on-Flash (MOD-3584)
• #2846 Enforce Redis Enterprise memory limit for vector indices.

v2.4.9

This is a maintenance release for RediSearch 2.4

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

Details

Bug fixes:

• #2837, #2836 crash on FT.AGGREGATE "... APPLY '-INF % -1'..."
• #2814 FT.EXPLAIN w/o parameters causes a crash
• #2790 Incorrect num_terms value in FT.INFO after a term is deleted from all the docs (Garbage Collection)
• #2804 Freeze when OFFSET+LIMIT was greater than maxSearchResults (config)
• #2791 Add BlockedClientMeasureTime to coordinator for more correct performance stats
• #2802 Tagged parts of keys (curly brackets {}) are now returned by FT.SEARCH.

Improvements:

• #2806 Do not load JSON API when RediSearch inits as a library

Minor breaking change

• As pointed out above, #2802 is a bug fix. However, if your application was relying on RediSearch wrongly trimming the tagged part of a key (using {}), this could break your application. This only applies to users who are using RedisSearch in clustered databases.

Release 2.4.8

This is a maintenance release for RediSearch 2.4

Update urgency: MODERATE: Program an upgrade of the server, but it's not urgent.
However, if you're using Vector Similarity (introduced in RediSearch 2.4), there are some critical bugs that may affect a subset of users. Please Upgrade!

Details

Bugfixes:

• #2739 Memory leak in coordinator related to Vector Similarity (MOD-3023)
• #2736, #2782 Memory allocation restrictions for Vector Similarity indices (causing OOM) (MOD-3195)
• #2755 Compare the entire vector field name instead of a prefix when creating a new vector index
• #2780 Init all vars in EvalContext (which might have led to crashes in clustered databases)

Improvements:

• #2740 Performance optimisation for hybrid vector queries