Resolving Typos and Facet Behavior in Typesense
TLDR Dima encountered unexpected behavior when searching with facets, but discovered the typo_tokens_threshold parameter to address the issue.
1
1Mar 13, 2023 (6 months ago)
Dima
02:18 PMI have a dataset with one string facet with values
facet1, facet2. If I search “foo bar” without chosen facets, it may return to me document {"facet": "facet1", "text": "foo ba"} and 0 in facet_count for facet2. But if I choose facet2 instead, it will show me more extreme typos, like fow bas. So it looks like typesense when nothing is found switching to more tolerant rules to try find anything. I checked and exhaustive_search is default in my caseDima
02:19 PMDima
02:25 PMtypo_tokens_threshold found it 🤓 Sorry to bother11
Typesense
Indexed 2764 threads (79% resolved)
Similar Threads
Facet Count Discrepancy in Integration Testing with Typesense
SamHendley faced an issue with inconsistent facet counts and found it was due to mixed case input and punctuation. Kishore Nallan confirmed that Typesense normalizes values before indexing, affecting the facet count. They then discussed addition of preconditioning data to match Typesense.
1Issues and Workarounds for Typesense's Typo Tolerance Feature
John found unexpected results with Typesense's typo tolerance feature. Jason explained it is the feature's design and suggested a workaround that could potentially yield more results than desired.
1Resolving 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.
1