[DOC] RediSearch usage with FTCreateParams and FTSearchParams classes #3934
Conversation
This file contains 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
uglide
approved these changes
Aug 23, 2024
| SearchResult sr = client.ftSearch("item-index", q); | ||
| ``` | ||
|
|
||
| Alternative searching using FTSearchParams: |
There was a problem hiding this comment.
In the field-level decoding PR we will need to change it to:
Alternatively, you can use FTSearchParams to access more advanced capabilities, such as field-level decoding control. Here is an example:
There was a problem hiding this comment.
@uglide IMO, we need a completely new example. I'm having difficulty making a decent example from title (text), body (text) and price (numeric) fields.
sazzad16
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.
No description provided.