Update RediSearch to 8.4 RC1 (v8.3.90)#14467
Merged
YaacovHazan merged 1 commit intoredis:unstablefrom Oct 27, 2025
Merged
Conversation
YaacovHazan
approved these changes
Oct 27, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(RediSearch/RediSearch#7076, RediSearch/RediSearch#6857) - Introducing
FT.HYBRID, a new command that enables hybrid queries combining both text and vector search, with support for RRF and LINEAR result combination. This update enhances performance and reliability through a more efficient networking layer, smoother query execution, and improved overall stability.(RediSearch/RediSearch#7065) - Add
search-default-scorerconfiguration to set the default text scorer across queries (by default it is BM25).RediSearch/RediSearch#7022 - Handle Atomic Slot Migration events upon moving slots from one node to another in a cluster mode.
(RediSearch/RediSearch#6769, RediSearch/RediSearch#6828, RediSearch/RediSearch#6877, RediSearch/RediSearch#6921) - Introduce query time memory guardrails by adding a new
search-on-oomconfiguration which defines the query engine behavior when OOM (Out Of Memory) is reached. OOM checks are applied toFT.SEARCH,FT.AGGREGATE, andFT.HYBRIDcommands. The behavior on OOM can be configured to one of three modes:IGNORE,FAIL, orRETURN.IGNORE- The default behavior, run queries anyway (not recommended for heavy queries returning a large result set).FAIL- Fail query execution immediately if any of the nodes are in OOM state when query execution starts.RETURN- A best effort appraoch to return partial results when OOM is detected in only some of the nodes in a cluster mode.