#community-help

Exact Token Matching Issue in Typesense

TLDR Saurabh had trouble in exact matching tokens in typesense resulting in an error. Jason suggested escaping the value using backticks to resolve the issue.

Powered by Struct AI
Oct 12, 2023 (1 month ago)
Saurabh
Photo of md5-57be9cd26696982f7dd2392eff28df99
Saurabh
11:37 AM
Hi everyone, exact match doesn't work with token separators? i.e "Integrated Courses (UG+PG)'" is not getting matched with "Integrated Courses (UG+PG)'" in typesense
Kishore Nallan
Photo of md5-4e872368b2b2668460205b409e95c2ea
Kishore Nallan
12:52 PM
When you say it doesn't match, are other results being returned along with this or does this result not appear at all?
Saurabh
Photo of md5-57be9cd26696982f7dd2392eff28df99
Saurabh
01:25 PM
gives 400 code error
Kishore Nallan
Photo of md5-4e872368b2b2668460205b409e95c2ea
Kishore Nallan
01:26 PM
Then that must some be some formatting issue. Please share a small reproducible snippet that I can run that reproduces the issue.
Saurabh
Photo of md5-57be9cd26696982f7dd2392eff28df99
Saurabh
01:30 PM
should i share the curl on ur DM
Kishore Nallan
Photo of md5-4e872368b2b2668460205b409e95c2ea
Kishore Nallan
01:31 PM
Need it on a small sample dataset with few records. It will be difficult to troubleshoot on your server because I can't debug it.
Saurabh
Photo of md5-57be9cd26696982f7dd2392eff28df99
Saurabh
01:36 PM
sharing it you on ur personal slack
Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
03:46 PM
The issue here with filter_by is that parentheses are used for precedence in the filter expression. So if you have parentheses in your filter value, you'd need to escape the value using backticks, like this:

"filter_by":"level_and_type:[Integrated Courses (UG+PG)]"

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Inconsistent Search Results in Typesense UI vs Dashboard

Abhishek reports inconsistent search results in the typesense UI vs dashboard integration when using page rank with Docusaurus plugin. Jason suggests creating a GitHub issue while Abhishek seeks clarification on prioritizing exact matches.

20
9mo

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.

6

111
8mo

Issue with Query Expectations on Typesense Search

Sean was having an issue with their search query on Typesense. Kishore Nallan suggested adjusting the 'drop_tokens_threshold' parameter. After making the adjustment, Sean found an issue with the order of the results, which was resolved by updating Typesense version.

2

22
2mo

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.

8

43
25mo

Resolving Typesense Search Issues

Conversation started by Maximilian about Typesense search behavior led to Users Kishore Nallan and Mike discussing and suggesting workaround, with Kishore Nallan promising an official solution soon. No final confirmation of resolution provided.

1

14
21mo