Josh Hall
03/30/2026, 7:21 PMjust enough, Just Enough Items comes up as expected
• When I search just e, it seems to match just and e separately, and the ranking is much worse
Is there a config for sequential or phrase-like matching, or anything along those lines that would help here?Jonathan King
03/30/2026, 8:18 PMprioritize_token_position would be one.Josh Hall
04/06/2026, 4:02 PM[
"name",
"indexed_name",
"slug",
"author",
"indexed_author",
"summary",
]
query_by_weights:
vec![15, 15, 10, 3, 3, 1]
prefix:
vec![true, true, true, true, true, true]
prioritize_exact_match: true
prioritize_num_matching_fields: false
text_match_type: max_weight
bucketing: buckets(5)Jonathan King
04/06/2026, 10:14 PMprioritize_token_position: true - this should make sure that results with 'just' at the front are ranked higher than ones with results starting with words with the letter e
• drop_tokens_threshold=0 - this will ensure that only words with both 'just' AND a word starting with e are matched.
If you let us know some more about what is bad about the rankings you're getting we could provide more options. The reason you're unexpected results is probably that by default Typesense takes the last word in the query and uses it as a prefix match, so it will be matching any word in your collection that starts with the letter e - which is probably a lot of words. This will be flooding your results and possibly be confusing rankings.Josh Hall
04/14/2026, 3:44 PMJosh Hall
04/14/2026, 3:46 PMJosh Hall
04/14/2026, 3:47 PM