Troubleshooting Facet Values Search Results Discrepancy
TLDR gab faced discrepancies with search results for different facet values. Kishore Nallan suggested upgrades and tweaks, partially resolving the issue. However, some inconsistencies remained.
Feb 11, 2022 (23 months ago)
gab
01:26 PMI have 2 facets values for a facet a field called
canton that are "Lucerne" | "Zurich"Whenever I send
q="lu" it find a document and also returns for highlights a matched tokens for "Lucerne"Whenever i send
q="zu" it find a document but it doesn't return for highlights a matched tokens for "Zurich"I didn't get yet why in the seond case it doesn't find the facet like in the first case
Kishore Nallan
01:36 PMgab
01:46 PMWould you see first some basic parameters that would influence this result :thinking_face:?
I have
num_typo:1 highlight_full_fields:trueKishore Nallan
01:47 PM0.23.0.rc27Kishore Nallan
01:47 PMgab
01:49 PMgab
01:49 PMgab
02:52 PMgab
02:52 PMgab
02:52 PMgab
03:01 PMBecause I have a
num_typo:1When i type
q="lu" I would expect both document come up. The one that exactly match with "Lucerne" and also the one with "Zurich" that has 1 typo tolerance, isn't it ?The same happen if I type
q="zu" only the document for Zurich will come up but not the one for "Lucerne"Kishore Nallan
03:08 PMtypo_tokens_threshold: 1 -> set this to 10 (previous value). That should produce the earlier behavior.Kishore Nallan
03:08 PMgab
03:56 PMtypo_tokens_thresholdMy config is:
typo_tokens_threshold: 10
min_len1_typo: 1I have stilll not have both facets that comes up
Feb 12, 2022 (23 months ago)
Kishore Nallan
01:46 AMKishore Nallan
07:13 AMlu and it returns both documents. Check the query parameters I have underlined in the screenshot.Feb 14, 2022 (23 months ago)
gab
12:19 PMIt looks like in your sample you're querying directly a "canton" collection.
Maybe my first message description was not so clear.
My collection is not directly a "canton" collection of documents.
I have a warehouses collection with inside, a facet field "canton"
Kishore Nallan
12:47 PM
Typesense
Indexed 3015 threads (79% resolved)
Similar Threads
Troubleshooting Typo Highlighting in Search Queries
Stefan queried "chews" and "Roche", despite having a typo distance of 4, was highlighted. Kishore Nallan requested to test on v0.20 RC. Random results like "Sachets" and "Lachesca" were also highlighted. On single record query, highlighting works. Kishore Nallan assured to address this issue in the pending release.
Handling Kinesis Stream Event Batching with Typesense
Dui had questions about how to handle Kinesis stream events with Typesense. Kishore Nallan suggested using upsert mode for creation/update and differentiating with logical deletion. After various discussions including identifying and resolving a bug, they finalized to introduce an `emplace` action in Typesense v0.23.
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.
Issues with Highlight Version in Typesense
Stefan reported issues with the new highlight version in Typesense. Kishore Nallan provided a temporary workaround and further fixed the issue with an updated build.
Query on Facet Values, `max_facet_values` , and `facet_query_num_typos`.
Jan asked about sorting facet values, managing `max_facet_values` and issues with `facet_query_num_typos`. Jason clarified the details on instantsearch widget handling of `max_facet_values` and identified a bug on the Typesense Server. Jason suggested a solution to the sorting issue.