Query Weighting Issue with 'Prioritize_Exact_Match'
TLDR John is facing issues with search results prioritizing lower query weights. Kishore Nallan explained it as a limitation in text match scoring, but agreed on the need for better scoring configuration.
Nov 09, 2022 (11 months ago)
John
01:30 PMprioritize_exact_match
behaviour, but even when I set that to false
it still comes first. Any ideas?Kishore Nallan
01:37 PMblue
and case
exist on different fields, that is considered lower text match score than a single field containing both words blue case
-- the weights come into picture only when text relevancy score is the same.John
01:54 PMprioritize_exact_match
would already doKishore Nallan
02:01 PMTypesense
Indexed 2779 threads (79% resolved)
Similar Threads
Relevancy Ordering Issue in Typesense
Ellen was having an issue with the relevancy ordering in Typesense. Jason suggested setting `prioritize_exact_match` to false and testing on version `0.24.0.rcn22`.
Sorting Search Results Based on Weights
Pantelis wanted to sort search results by weight. Kishore Nallan suggested using "prioritize_exact_match: false" and "text_match_type: 'max_weight'" to achieve the desired result.
Issues With `text_match` Scoring for Search Queries in Typesense
Colin encountered issues with the `text_match` scoring on Typesense v0.23.1. Jason and Kishore Nallan identified a potential issue with numeric overflow in the text match score and applied an unverified patch. The final resolution is unclear.