Clarification on `filter_by` Argument in Typesense Documentation
TLDR Gabe asked if filter_by
in Typesense accepts OR arguments, which Jason confirmed. Gabe then suggested adding this clarification to the documents.
1
1
Jun 25, 2021 (29 months ago)
Gabe
08:47 PMfilter_by
:> For eg:
category:=Shoe
will match documents from the category shoes and not from a category like shoe rack
. You can also filter using multiple values: category:= [Shoe, Sneaker]
.Is this an OR? i.e. it returns results that have either a category of "Shoe" or "Sneaker" (or both)?
Jason
08:48 PMGabe
08:49 PMGabe
08:49 PMJason
08:51 PM1
1
Typesense
Indexed 2786 threads (79% resolved)
Similar Threads
Discussing Filter Operators in Typesense
Roshan asked about the functionality of the 'contains' operator in Typesense filters. Kishore Nallan explained how to use the operator and suggested using a curl query for better insight into the issue. However, the thread ends without a resolution.
Understanding `filter_by` Functionality in Typesense
Harpreet had questions about `filter_by` function from the documentation. Kishore Nallan clarified that marking field as a facet isn't needed in 0.22. They also explained the difference between contains check and strict check.
Querying Typesense API with Array of Strings
Nikhilesh was struggling to query the typesense API with an array of strings. Kishore Nallan clarified the issue might be related to url encoding and further explained how to properly use the `q` and `filter_by` parameters.