fix: Use parameter substitution for vector data in hybrid search #455
+54
−19
Conversation
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
Collaborator
|
@vishal-bala Let's stick to conventional commits for our repos https://www.conventionalcommits.org/en/v1.0.0/ (you can just give the PR name a conventional commit and we can "squash and merge" |
vishal-bala
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Support for inlined blobs was dropped in FT.HYBRID due to some sequences being misinterpreted (see RediSearch/RediSearch#7768). This PR updates the hybrid search implementation to pass vector data to hybrid searches via parameter substitution instead.