Addressing Issues with Address Search Synonyms in Typesense
TLDR chase noted issues with typesense address synonyms on their platform. Jason suggested altering the synonym settings and later to upgrade to a later version. Despite resolving the initial issue, the upgrade spiked latency times. Further investigation is ongoing.
1
1
Aug 04, 2023 (2 months ago)
chase
11:33 PMweāre having some issues with the way that typesense is handling synonyms on our platform, leading to less than desirable first, second and third results for a given search. our records are address records, and hereās an example of the issue:
for the address 1370 S Ocean BLVD APT 405 Pompano Beach FL 33062, some users might like to input UNIT instead of APT - but having a synonym between these two doesnāt seem to work. even just not having that unit/apt/# there all together seems to work, but having something like UNIT there instead of APT will cause other random addresses with different numbers to rank first, even though none have āunitā anywhere in the record. any ideas? happy to clarify further if needed - thanks in advance!
Jason
11:42 PMYou want to set that up as a multi-way synonym. So leave the root field empty, and add āAPT, UNITā in the synonyms field
Jason
11:43 PMchase
11:45 PMchase
11:46 PMJason
11:47 PMchase
11:49 PMchase
11:49 PMchase
11:50 PMJason
11:52 PMchase
11:52 PMJason
11:53 PM0.25.0.rc60
as the version1
chase
11:53 PM1
Aug 09, 2023 (1 month ago)
chase
06:55 PMJason
06:57 PMmulti_search
, copy as curl and DM it to me? We can then take a closer lookTypesense
Indexed 2779 threads (79% resolved)
Similar Threads
Resolving Multilingual Search Function in Typesense Software
Bill is having difficulty with multilingual search functionality in Typesense software. Developer Kishore Nallan suggested setting a language locale and provided a demo build. The build solution had some issues, and after multiple rounds of software updates and troubleshooting, the problem still persists.
Optimizing Typesense Implementation for Large Collections
Oskar faced performance issues with his document collection in Typesense due to filter additions. Jason suggested trying a newer Typesense build and potentially partitioning the data into country-wise collections. They also discussed reducing network latency with CDN solutions.
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.
Resolving Issues with Infix and Prefix in Query Searches
Daren struggled with searches missing values in production. Jason and Kishore Nallan offered insights and created new features to help solve the problem, which was then tested and deployed by Daren.
Querying Issues with Newly Created Collection
User Dima reported issues with missed search results in a new collection he created. User Kishore Nallan offered solutions but the problem persists. Dima cannot share the data, which makes it harder to resolve the issue.