#community-help

Querying Normalized Typesense Index Results in Unexpected Matches

TLDR Jonathan questioned if queries should return "jill" and Turkish "jıll" when searching for "jill". Jason confirmed this is expected but suggested opening a GitHub issue for their specific use case which Jonathan completed.

Powered by Struct AI

1

Jan 19, 2023 (11 months ago)
Jonathan
Photo of md5-1ac34e3717bc718eb955ab69034d52d6
Jonathan
07:24 PM
Is it expected for queries, even with ?num_typos=0, to return both jill and jıll (turkish i) when searching for jill, if your indexed data has the "dotless i" (turkish) https://www.compart.com/en/unicode/U+0131 ?

[
  { "name": "jill" },
  { "name": "jıll" }
]
Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
07:26 PM
Typesense normalizes those internally so jıll gets indexed as jill… So it’s expected behavior, at least at the moment.
07:26
Jason
07:26 PM
Does that not work for your use-case?
Jonathan
Photo of md5-1ac34e3717bc718eb955ab69034d52d6
Jonathan
07:27 PM
use-case is username search for making a payment, so a fuzzy match obviously would be bad
07:28
Jonathan
07:28 PM
this issue is somewhat similar: https://github.com/typesense/typesense/issues/262#issuecomment-844631342 but it was solved via the num_typos
Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
07:29 PM
Hmmm, username search for payments is a good use case. Could you open a GitHub issue reporting this, along with your use case?
07:29
Jason
07:29 PM
CC: Kishore Nallan
Jonathan
Photo of md5-1ac34e3717bc718eb955ab69034d52d6
Jonathan
07:29 PM
yep, and ty for quick response (as usual)

1

Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
07:57 PM
Perfect, thank you!

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

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

Solving Typesense Cloud Interface Issue in Python

Orion had an issue querying from Python in the Typesense Cloud interface. Kishore Nallan identified the problem within the array declaration. They then discussed improving error messages and Orion offered to make a PR.

6

47
14mo

Cold Start Problem with Dynamic Collections

Adrian reported cold start issues with dynamic collections. Jason suggested using wildcard `*` for query_by parameters, upgrading to `0.25.0.rc34`, and clarified conventions. Adrian's issues were resolved but they reported a limitation that will potentially be addressed.

6

39
6mo

Querying with Typesense-Js and Handling Null Values

michtio was querying using typesense-js and receiving fewer results than expected. Kishore Nallan suggested using different query parameters. Further discussion led to the handling of 'null' values and filtering syntax in the search queries. The thread ended with Jason offering migration support from Algolia to Typesense.

4

39
17mo

Array Field Autocomplete Issue in Typesense Migration

Kanwei encountered issues with autocomplete when migrating from Elasticsearch to Typesense. Jason and Kishore Nallan identified it as a bug and instructed Kanwei to create a GitHub issue.

1

20
9mo