Configuring Exact Search Matches and Usage of Separators in Typesense
TLDR Ivan needed help with obtaining exact matches on Typesense. Jason suggested to turn off prefix matches and Kishore Nallan advised using separators config. They helped Ivan understand searching via variations and the upcoming "space as typo" feature.
1
Dec 13, 2021 (25 months ago)
Ivan
04:35 PMIn our collection we have facet field "uri", i am trying to find exact match "estg-9" in this field, but instead i get results like "estg-91", "estg-92","estg-9a", etc. Is there any way to get exact matches?
Jason
04:36 PMJason
04:37 PMIvan
04:39 PMDec 14, 2021 (25 months ago)
Ivan
09:39 AMI have uri like: "estg-9" , and now with turned off prefix i can find this exact match entering "estg-9", but how can i configure search to also find this "estg-9" by entering for example "9 estg" or "estg 9" ?
Kishore Nallan
09:50 AM1
Ivan
09:51 AMDec 20, 2021 (25 months ago)
Ivan
12:00 PMKishore Nallan
12:02 PMestg 9
should become estg9
for searching (however, 9estg
will not work since will be order dependent).Kishore Nallan
12:03 PM["estg-9", "estg9", "9estg"]
etc.Ivan
12:05 PMIvan
01:17 PMKishore Nallan
01:18 PMIvan
01:22 PMKishore Nallan
01:26 PMTypesense
Indexed 3011 threads (79% resolved)
Similar Threads
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.
Troubleshooting Issues with DocSearch Hits and Scraper Configuration
Rubai encountered issues with search result priorities and ellipsis. Jason helped debug the issue and suggested using different versions of typesense-docsearch.js, updating initialization parameters, and running the scraper on a Linux-based environment. The issues related to hits structure and scraper configuration were resolved.
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.
Adjusting Text Match Score Calculation in TypeSense
Johannes wanted to modify the Text Match Score calculation in TypeSense to improve search results returns. With counsel from Jason and Kishore Nallan, various solutions were proposed, including creating a Github issue, attempting different parameters, and updating Docker to a new version to resolve the matter.
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.