Steven Xu
11/20/2024, 10:23 PMSteven Xu
11/20/2024, 10:25 PM_eval(status:active),_text_match:desc
Steven Xu
11/20/2024, 10:30 PM578730089005449300
) but I'm not sure what the lower and upper bounds areJason Bosco
11/20/2024, 11:22 PMI'm overriding the text match sort and I'm seeing higher scores at the bottom of the query results.This is because
_eval(status:active),_text_match:desc
explicitly places active status results on top, ignoring text relevance score. Then within each bucket (1) results that match the filter (2) results that don't match the filter, the value for the eval
is tied, so then the text match score is used to break the tie.
You probably want something like _text_match(buckets: 10):desc, _eval(status:active)
to achieve what you're looking to do.
The bucketing mechanism is described here: https://typesense.org/docs/guide/ranking-and-relevance.html#ranking-based-on-relevance-and-popularityJason Bosco
11/20/2024, 11:24 PMSteven Xu
11/21/2024, 12:40 AM_text_match(buckets: 10):desc, _eval(status:active)
would produce results with both active and inactive, ordered by text relevance scoreJason Bosco
11/21/2024, 12:45 AMSteven Xu
11/25/2024, 7:23 AMtext_match_info
? It would be quite useful knowing the relative difference between results, and further modifying it after processing results. I'm currently querying by text_match_type:max_weight
I'm mainly looking to assign scores to my results, if fetching the score is not possible do you recommend another method to assign scores to results?Jason Bosco
11/25/2024, 5:13 PMSteven Xu
11/25/2024, 5:24 PMTextMatch *int64
is the only score I seeJason Bosco
11/25/2024, 5:25 PMSteven Xu
11/25/2024, 5:31 PMJason Bosco
11/25/2024, 5:32 PMSteven Xu
11/25/2024, 5:33 PM