#community-help

Adjusting Token Order Impact in Query String

TLDR David asked about adjusting the impact of token order in the query string. Jason advised using a parameter named prioritize_token_position.

4mo

Join the chat

Jul 18, 2023 (4 months ago)

Photo of md5-94c93df7325e8fde185c76c659656ee9

David

09:59 PM

Is there a way to adjust the impact of token order in the query string? For instance, if you are searching “headquarters google”, google would be underweight relative to headquarters.

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

10:16 PM

There’s a parameter called prioritize_token_position that does this

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Tuning Query Results Order with Query_by_Weights

Nathan is trying to tune the order of results using `query_by_weights`, but experiences a smaller impact than expected. Jason suggests trying `max_weight` and sharing a snippet to further investigate.

6mo

Issue with Typo Correction/Prefix Search and the Role of max_candidates

John noticed inconsistent search results based on max_candidates settings, and Kishore Nallan clarified its role for multi-word queries. They resolved that increasing max_candidates ensures the query isn't prematurely limited.

18mo

Inconsistent Search Results in Typesense UI vs Dashboard

Abhishek reports inconsistent search results in the typesense UI vs dashboard integration when using page rank with Docusaurus plugin. Jason suggests creating a GitHub issue while Abhishek seeks clarification on prioritizing exact matches.

9mo