RediSearch 2.6 release notes
Requirements
RediSearch v2.6.15 requires:
- Minimum Redis compatibility version (database): 6.0.16
- Minimum Redis Enterprise Software version (cluster): 6.2.8
v2.6.15 (December 2023)
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 theWITHCURSOR
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)
- #4244, #4255 Profiling
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) ofUNION
(OR) (MOD-5910)
v2.6.14 (November 2023)
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 inFT.AGGREGATE
onDIALECT 3
(MOD-5041) - #3823
APPLY
orFILTER
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 sinceCURSOR
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 GC could corrupt unique values (MOD-5815)
- #4002 Setting a low
MAXIDLE
parameter value inFT.AGGREGATE
causes a crash (MOD-5608)
- #3783 Broken lower and upper
Security and privacy:
- #3844 Limits maximum phonetic length to avoid vulnerability (MOD 5767)
v2.6.12 (July 2023)
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:
- #3557
TIMEOUT
configuration onFT.AGGREGATE
query being ignored (MOD-5208) - #3552
FT.CURSOR READ
onJSON
numeric queries not returning results (MOD-4830) - #3606 Update numeric inverted index
numEntries
avoiding excessive memory consumption (MOD-5181) - #3597 Duplicating alias as output name on
FT.AGGREGATE
reducer (REDUCE
argument) doesn’t return results (MOD-5268) - #3654 Added check for
@
prefix onGROUPBY
fields returning an error instead of wrong results
- #3557
Improvements:
v2.6.9 (April 2023)
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:
Improvements:
v2.6.6 (March 2023)
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:
- #3403 Fix suffix and prefix matching when using
CASESENSITIVE
flag (MOD-4872)
- #3403 Fix suffix and prefix matching when using
Improvements:
- #3397 Improve the Vecsim initial capacity default value
v2.6.5 (February 2023)
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:
Improvements:
- #3361 Enable the use of IPv6 for all cluster and module communication
v2.6.4 (December 2022)
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:
Improvements:
v2.6 GA (v2.6.3) (November 2022)
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 requested feature 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.
What’s new in 2.6
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 an array of strings 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:
- #2886 Support for wildcard queries for TEXT and TAG fields, where
Bugs (since 2.6-RC1 / v2.6.1):