Synonym Issue with Multiple Word Query
TLDR John observed inconsistent search results involving synonyms and raised the issue. Kishore Nallan admitted the bug and asked John to create Github issues, promising to prioritize the multi-synonym bug.
1
1
Nov 15, 2022 (11 months ago)
John
01:07 PMAre there any known issues with multiple synonyms in a query?
Kishore Nallan
01:34 PMJohn
02:23 PM> Got 1 results for “blazer male” (Should match immediately)
> Got 0 results for “blazer man” (Should match with synonym male<->man)
> Got 0 results for “suit male” (Should match with synonym blazer<->suit)
> Got 1 results for “suit man” (Should match with synonyms blazer<->suit and male<->man)
John
02:23 PMKishore Nallan
02:40 PM1
Nov 16, 2022 (11 months ago)
John
09:21 AM> Got 1 results for “trousers” (Should match immediately)
> Got 1 results for “trouesrs” (Should match by allowing misspelled words <trouser>)
> Got 1 results for “pants” (Should match with synonym trousers<->pants)
> Got 0 results for “patns” (Should match misspelled <pants> synonym to <trousers>)
Kishore Nallan
12:38 PMRegarding
patns -- that's expected because we don't apply synonyms on typo corrected variations of the query. This is to prevent false positives from happening.John
12:45 PM> Regarding
patns -- that’s expected because we don’t apply synonyms on typo corrected variations of the query. This is to prevent false positives from happening.Understand, seems quite context-specific though, could be exposed as a flag!
Kishore Nallan
12:48 PMWill try to prioritize the multi-synonym bug fix first. I've to see what kind of effort is involved. Currently, both matching synonyms are swapped so you end up with a variation that doesn't exist. Need to see how to account for all variations (both swapped, first word swapped, second word swapped). Gets more complicated when query string is larger and several words match: might generate too many combinations.
John
12:49 PM
Typesense
Indexed 2786 threads (79% resolved)
Similar Threads
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.
Issues with Repeated Words and Hyphen Queries in Typesense API
JinW discusses issues with repeated word queries and hyphen-containing queries in Typesense. Kishore Nallan offers possible solutions. During the discussion, Mr seeks advice on `token_separators` and how to send custom headers. Issues remain with repeated word queries.
Resolving Typesense Result Issue in Document Collection Queries
Mike was encountering errors when searching for specific query in their Typesense document collection. Jason suggested it may be due to the `drop_tokens_threshold` setting. There was a misunderstanding but after further explanation from Jason, Mike understood and decided to continue the conversation via email.
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.
Phrase Match Problem in Typesense Version 0.24.0rcn25
Robert was unsure about correct phrase match usage in Typesense. After providing Kishore Nallan with necessary data, Kishore Nallan was able to replicate the issue. Robert shared a Github link for further tracking, where Kishore Nallan responded later.