hi all! hoping this question can fit into a slack ...
# community-helpc
chase edson
08/04/2023, 11:33 PMhi all! hoping this question can fit into a slack thread, but let me know if i should move it into an email conversation 🙂
we’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!
j
Jason Bosco
08/04/2023, 11:42 PMIf I’m looking at the right cluster, I see a one-way synonym setup for APT (root) -> UNIT… this will only kick in when the user types in apt.
You 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 Bosco
08/04/2023, 11:43 PMOr if you only want Unit to map to apt, and not the other way around, you want to swap the root and synonym in the setup
c
chase edson
08/04/2023, 11:45 PMthanks for the reply - i was testing with that earlier. unfortunately, i get the same type of result with that setup
chase edson
08/04/2023, 11:46 PMmessage has been deleted
j
Jason Bosco
08/04/2023, 11:47 PMCould you try setting the synonyms all lower-case? There’s a bug in 0.24.1 that makes synonyms and overrides case-sensitive only during synonym resolution when they shouldn’t be… since during query parsing we lower-case all strings
c
chase edson
08/04/2023, 11:49 PMinteresting, good to know. unfortunately seems like the same result still:
chase edson
08/04/2023, 11:49 PMshouldn’t it still be matching the “101” after unit though?
chase edson
08/04/2023, 11:50 PMif i don’t include unit/apt at all, it matches properly:
j
Jason Bosco
08/04/2023, 11:52 PMCould we try upgrading you to the latest RC build to see if some of the tangentially related issues we’ve fixed around synonym resolution addresses this use-case?
c
chase edson
08/04/2023, 11:52 PMsure! we’ve got a production one in there that i’d rather not touch, do you need the ID of the cluster i’d want to upgrade?
j
Jason Bosco
08/04/2023, 11:53 PMYou can actually do the upgrade from Cluster Configuration > Modify. You want to pick
0.25.0.rc60❤️ 1
c
chase edson
08/04/2023, 11:53 PMwill try and report back, thanks
đź‘Ť 1
chase edson
08/09/2023, 6:55 PM@Jason Bosco updating resolved the issue - but unfortunately now our latency times are dramatically increased on this build (avg of 10 seconds instead of 300-400ms) any ideas? should i try rebuilding the cluster?
j
Jason Bosco
08/09/2023, 6:57 PMHmmm, that’s not good. Could you open the network tab in the browser dev console, do the search query, look for a request to
multi_search