Hi all - really enjoying typesense so far! Occasionally running into an issue with relevancy ordering. It seems that when

prioritize_exact_match

is set to true, it weights exact matches very heavily in the scoring. As a simplified example, if we have records with two fields - title and tags - the desired behavior would be to have exact matches for title show up first, then inexact matches for title, then exact matches for tags, etc. However because

prioritize_exact_match

is weighted so much heavier compared to the

query_by_weights

, we can’t achieve this even if the title is weighed at 127 and the tag is weighted at 1. Any ideas on ways to work around this? As an aside it would be great if

prioritize_exact_match

was a numerical value so there could be more flexibility!

Could you try setting

prioritize_exact_match

to false?

yep our current plan is to set it to false, just curious if there were any other solutions since ideally we would give slight preference to exact matches. But sounds like setting to false is probably the way to go.

Typesense should give priority to exact matches in a particular field by default, based on weight. We added

prioritize_exact_match

to override this behavior across fields, so regardless of weight, if an exact match occurs it will be prioritized when this flag is true

ah ok that makes sense, thank you!