Extracting Typos & Dropped Tokens Info from Search Results
TLDR Dima wants to extract info about applied typos/dropped tokens from search results. Jason offers suggestions and encourages creating a GitHub issue for more structured information. Dima creates the issue.
Jun 14, 2023 (3 months ago)
matched_tokenskey in the response and compare it to the query that the user typed
matched_tokensmay contain more elements than query tokens
Indexed 2779 threads (79% resolved)
Troubleshooting "drop_tokens_threshold" and Typo Tolerance in Typesense
Joe had issues with "drop_tokens_threshold" = 0 and typo tolerance in Typesense, after which Kishore Nallan provided solutions and clarifications on feature functionality. Their issues with the search result limit and tokens were resolved after discussion and testing.
Phrase Search Relevancy and Weights Fix
Jan reported an issue with phrase search relevancy using Typesense Instantsearch Adapter. The problem occurred when searching phrases with double quotes. The team identified the issue to be related to weights and implemented a fix, improving the search results.
"Query By" Parameters Resulting in Fewer Search Results
Jon encountered unexpected behavior with "query by" parameters. Upon checking the post request body by Jason, Kishore Nallan noted the issue originates from the typo match with "full stack". Suggested solution was setting `split_joins_tokens: always`.
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.
Resolving Typesense Search Issues
Conversation started by Maximilian about Typesense search behavior led to Users Kishore Nallan and Mike discussing and suggesting workaround, with Kishore Nallan promising an official solution soon. No final confirmation of resolution provided.