content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-1.4-release-notes.md
RediSearch v1.4.28 requires:
This is a maintenance release for version 1.4.
Headlines:
Details:
Headlines:
Details:
exists function that can be used on conditional updates REPLACE PARTIAL to check if a field exists in the document.Headlines:
Details:
FORK GC crash which caused by accessing uninitialized variable.Headlines:
Details:
NOINDEX fields.FORK GC was not updating the unique sum of the numeric index.Headlines:
Details:
Headlines:
Details:
Headlines:
Details:
Headlines:
Details:
NOINDEX fields.Update urgency: Medium This is a maintenance release for version 1.4.
This release improves overall stability and provides fixes for issues found after the previous release.
GC run.FT.AGGREGATE on non-existing index.GC run.FT.AGGREGATE.Update urgency: Medium This is a maintenance release for version 1.4.
This release improves overall stability and provides fixes for issues found after the previous release.
Update urgency: Medium This is a maintenance release for version 1.4.
This release improves overall stability and provides fixes for issues found after the previous release.
Update urgency: Medium This is a maintenance release for version 1.4.
This release improves overall stability and provides fixes for issues found after the previous release.
to_number() and to_str() functions for ambiguity reasonsINFO MEMORY command.Update urgency: Medium This is a maintenance release for version 1.4.
This release improves overall stability and provides fixes for issues found after the previous release.
Main features:
FORK_GC_CLEAN_THRESHOLD. RediSearch will only start to clean when the number of not cleaned documents is exceeding this threshold.Main Fixes:
Update urgency: Medium This is a maintenance release for version 1.4.
This release improves overall stability and provides fixes for issues found after the previous release.
Main Fixes:
Update urgency: Medium This is a maintenance release for version 1.4.
This release improves overall stability and provides fixes for issues found after the previous release.
Main Fixes:
Update urgency: Medium This is a maintenance release for version 1.4.
This release improves overall stability and provides fixes for issues found after the previous release .
Main Fixes:
Update urgency: Medium This is a maintenance release for version 1.4.
This release improves overall stability and provides fixes for issues found after the previous release .
Main features:
Main Fixes:
Update urgency: Medium
This release only add support for aliasing to the previews 1.4.10 release.
Update urgency: Medium
This is a maintenance release for version 1.4.
This release improves overall stability and provides fixes for issues found after the previous release .
Main Fixes:
Update urgency: Medium
This is a maintenance release for version 1.4.
This release improves overall stability and provides fixes for issues found after the previous release .
Main Fixes:
Known Issue:
Update urgency: Low
Technical release, no changes nor fixes.
Update urgency: Medium
This is a maintenance release for version 1.4.
This release improves overall stability and provides fixes for issues found after the previous release .
Main Fixes:
Update urgency: Medium
This is a maintenance release for version 1.4.
This release improves overall stability and provides fixes for issues found after the previous release .
Main Fixes:
REPLACE PARTIAL might not work properly (#621)Update urgency: Low
This is a maintenance release for version 1.4.
This release improves overall stability and provides fixes for issues found after the previous release .
Main Fixes:
Update urgency: Low
This is a maintenance release for version 1.4.
This release improves overall stability and provides fixes for issues found after the previous release .
Main Fixes:
Update urgency: Low
This is a maintenance release for version 1.4.
This release improves overall stability and provides fixes for issues found after the previous release .
Main Fixes:
Update urgency: Low
This is a maintenance release for version 1.4.
This release improves overall stability and provides fixes to issues found.
Update urgency: Medium
This is a maintenance release for version 1.4, with the next version planned for release being 2.0.
This release improves overall stability and focuses on performance improvements of the garbage collector. It also includes:
RediSearch employs a garbage collector that removes deleted documents from the internal data structures.
In this release the garbage collection mechanism was improved in terms of efficiency, i.e. the amount of memory it reclaims, as well as in terms of performance (i.e. it is faster). The improved mechanism uses forked threads. Additional details can be found in this post: How We Increased Garbage Collection Performance with RediSearch 1.4.1.
The improved collection mechanism is currently *experimental- and is not enabled by default. Enabling the new garbage collection mechanism requires setting the GC_POLICY configuration option to FORK at load time, for example:
redis-server --loadmodule ./redisearch.so GC_POLICY FORK
RediSearch's [configuration]({{<relref "/develop/ai/search-and-query/administration/configuration">}}) is applied via arguments passed to the module at load time. This release introduces the new FT.CONFIG command that allows to retrieve the current configuration as well as change it during runtime.
This version removes the limit of 10 results from FT.SUGGET - you can set the MAX num as high as needed.
**Update urgency:*- Medium - mainly due to numerous fixes
This version improves overall stability and performance of RediSearch. It also delivers better support for use cases in which documents are continuously updated. New features:
Like most search engines, RediSearch was designed for maintaining append-mostly indices. To update an existing document, the document is actually replaced - that is deleted and added to the index.
Because RediSearch provides realtime indexing and searching, it is sometimes used to search near-realtime data (or the results of its processing). In such cases, the number of indexed documents stays mostly static, but their contents are continuously updated.
To support this use case, RediSearch has been reworked internally to use 64-bit internal document IDs so that an index can sustain high update throughputs without overflowing. Furthermore and as a result, significant effort has been put into improving memory management and garbage collection.
The IF subcommand has been add to FT.ADD. When used with the existing REPLACE [PARTIAL] subcommand, the document will be updated only if the condition provided evaluates to a truth value, otherwise a special NOADD reply is returned.
The FT.ALTER command has been introduced, and provides the ability to add new fields to the definition of an existing index. The contents of such newly-added fields are indexed only for new or updated documents.
Query spelling correction, a.k.a "did you mean", is now provided via the FT.SPELLCHECK command. It enables generating suggestions for search terms that could be misspelled. For more details see [Query Spelling Correction]({{<relref "/develop/ai/search-and-query/advanced-concepts/spellcheck">}}).
Phonetic matching, a.k.a "Jon or John?", is now supported via the PHONETIC text field attribute. The terms in such fields are also indexed by their phonetic equivalents, and search results include these by default. For more details see [Phonetic Matching]({{<relref "/develop/ai/search-and-query/advanced-concepts/phonetic_matching">}}).
The fuzzy match operator, '%', can now be repeated up to three times to specify the Levenshtein distance. That means that the queries %hello%, %%hello%% and %%%hello%%% will perform fuzzy matching on 'hello' for all terms with LD of 1, 2 and 3, respectively.