Releases: RediSearch/RediSearch
2.2 GA (v2.2.5)
This is the General Availability release of RediSearch 2.2.
Headlines
Searching and indexing JSON documents
This release introduces the ability to index, query, and full-text search JSON documents using JSONPath queries.
On the schema creation FT.CREATE, it is now possible to map a JSONPath query with a field. When a JSON document is indexed, the value extracted by the JSONPath query is indexed in the given field.
This features require the module RedisJSON 2.0 to be installed.
Profiling queries
With the new FT.PROFILE command it is now possible to profile in detail the execution time of several internal steps involved in the execution of FT.SEARCH and FT.AGGREGATE.
That way, it is possible to understand which part of the query is taking most of the resources.
Field aliasing
With the support of JSON document indexing, It is now possible to map a JSONPath query to an alias. Therefore, it is possible to index the same value in different fields with different indexing strategies.
Details
Enhancements
- Add support for redis COPY command (#2337)
- Add
LOAD *
for FT.AGGREGATE (#2243) - Add multi value recursive decent tag (#2207)
- Add UNF flag for SORTABLE fields (#2188)
- LLAPI getter functions for score, language and stopwords list (#2184)
- JSON array can be stored in a TAG field (#2133)
- Improve FT.INFO complexity to O(1) (#2153)
- Add CASESENSITIVE to TAG fields (#2138)
- FT.INFO has identifier and attribute for fields (#2137)
Bug fixes
- Fix score field for JSON (#2341)
- Fix escaping for tags (#2325)
- Remove empty tag values (#2269)
- Replace NULL with empty iterator for child of negative iterator (#2223)
- Update field limit on tags (#2215)
- Partial JSON documents are not indexed (#2143)
- Field loaded with 'AS' cant be used by funcs (#2109)
Notes:
This is the first GA version of 2.2. The version inside Redis will be 2.2.5 in semantic versioning.
Since the version of a module in Redis is numeric, we could not add a GA flag.
2.0.13
This is a maintenance release for RediSearch 2.0.
Update urgency: MODERATE
: Program an upgrade of the server, but it's not urgent.
Details
Bug fixes:
- #2269 #2291 Remove TAG values from trie with no entries on Garbage Collection.
- #2287 Uninitialized read on
FT.ADD
- #2342 Check for NULL result on intersect iterator
- #2350 Crash on
FT.AGGREGATE
withLIMIT 0 0
Improvements:
- #2243 Add
LOAD *
for FT.AGGREGATE which will load all fields
2.0.12
This is a maintenance release for version 2.0.
Update urgency: MODERATE
- Program an upgrade of the server, but it's not urgent.
Details:
-
Enhancements:
- #2184 API: getter functions for score, language and stop words list
- #2188 Introduced the UNF parameter to SORTABLE to disable normalisation on TAG/TEXT fields
- #2218 API: added RediSearch_CreateDocument2
-
Bug fix:
2.0.11
This is a maintenance release for version 2.0.
Update urgency: LOW
- No need to upgrade unless there are new features you want to use.
Headlines:
This release improves overall stability and provides fixes for issues found after the previous release.
Details:
-
Enhancements:
- #2156 TAG fields can now be case sensitive using the CASESENSITIVE parameter
- #2113 An already existing document that can't be updated is removed from the index, (JIRA MOD-1266)
-
Enhancements on RSCoordinator:
-
Bug Fixes:
2.0.10
This is a maintenance release for version 2.0.
Update urgency: HIGH
- There is a critical bug that may affect a subset of users. Upgrade!
Details:
-
Enhancements:
-
Bug fix:
-
Bug fix on RSCoordinator:
- #257 Switch coordinator to send _FT.CURSOR instead FT.CURSOR to prevent data access without holding the lock
2.2-RC1
This is the first release candidate for RediSearch 2.2
Highlights
This release adds the following main feature:
Indexing, querying and full-text search of JSON documents
Until now, RediSearch has been providing indexing and search capabilities on hashes.
Going forward, by exposing its capabilities to other modules, RedisJSON gives RedisSearch the possibility to index JSON documents.
Another feature part of this release is the ability to profile queries (FT.PROFILE).
This feature will increase the developer experience by empowering them to understand the query execution of RediSearch queries and allow them to optimise them.
Lean more by reading the blog post: Indexing, querying and full-text search of JSON documents with Redis
Getting started:
The easiest way to discover these new features is by using this Docker image. The docker image is publically available and contains Redis together with the main Redis modules, including RediSearch and RedisJSON
docker run -p 6379:6379 redislabs/redismod:preview
For more details read the dedicated page about JSON indexing.
Notes:
- Requires Redis v6 or above
- Requires RediJSON 2.0-RC1 for JSON support
- This is not the GA version of 2.2. The version inside Redis will be 20200 or 2.2.0 in semantic versioning. Since the version of a module in Redis is numeric, we could not add an RC1 flag.
- For production usage, please use RediSearch 2.0.
1.6.16
This is a maintenance release for version 1.6.
Update urgency: MODERATE
- Program an upgrade of the server, but it's not urgent.
Details:
- Bug fix:
- #2018: FT.ADD REPLACE leaves fields from the previous document that are not included in the new document #647 #1193
2.0.9
This is a maintenance release for version 2.0.
Update urgency: SKIP
- There are new critical issues introduced by this release. Skip or Upgrade ASAP.
Known issue: This release contains a major bug when it is used with RSCoordinator #259 #275.
In this case we recommend to skip this version and stick to v2.0.8. This issue will soon be fixed in v2.0.10.
Details:
- Bug fix on RSCoordinator:
- #259: Fix deadlock on cursor read by performing cursor command on background thread
- Other changes:
- Build fixes
- Documentation fixes
2.0.7
This is a maintenance release for version 2.0
Update urgency: Medium
Details:
-
Major enhancements:
-
Major bugfix:
-
Minor bugfixes:
2.0.8
This is a maintenance release for version 2.0.
Update urgency: HIGH
: There is a critical bug that may affect a subset of users. Upgrade!
This release fixes an important regression introduced by the 2.0 release. The payload is supposed to be returned only when the WITHPAYLOADS parameter is set.
Details: