Clarification on "prioritize_exact_match" Parameter
TLDR Jeremie queried about the "prioritize_exact_match" parameter in Typesense. Kishore Nallan suspected the duplicate words in the query were the problem, and this was confirmed by Jeremie. A Github issue was created for tracking.
Oct 24, 2023 (1 month ago)
The documentation says clearly that it depends on a “particular field value verbatim”, but from my tests it seems any document that matches all the searched tokens is considered an exact match, right ? Did I misunderstood something here or the only way to make this work is having a “title_length” field on the side and tie-order on this field ?
> By default, if the search query matches a particular field value verbatim, Typesense deems that document to have the highest relevancy and prioritizes it.
Kishore Nallan04:06 PM
asin the query to be the issue here. Can you verify that? Can you also please create an issue on Github for us to track?
Oct 25, 2023 (1 month ago)
Indexed 3011 threads (79% resolved)
Issue with Query Expectations on Typesense Search
Sean was having an issue with their search query on Typesense. Kishore Nallan suggested adjusting the 'drop_tokens_threshold' parameter. After making the adjustment, Sean found an issue with the order of the results, which was resolved by updating Typesense version.
Typesense Partial Text Search Functionality Clarification
Davi queries about search behavior in Typesense, not seeing expected results with partial search strings. Jason confirms this behavior as expected and refers to an open feature request to address the query.
Prioritizing Search Mechanisms in Typesense
Roman asked if there was a way to prioritize searches in 'foo' over 'bar' in Typesense. Jason clarified that only sequential searches would satisfy this. Yoann suggested batching the requests.