#community-help

Handling Hyphenated Terms in Search Queries

TLDR A asked about search support for hyphenated terms. Jason advised to add hyphen in the token separators config to index them as two words.

23mo

Join the chat

Feb 05, 2022 (23 months ago)

Photo of md5-fe034fbff44e9cae037b7bb23a5080c4

A

05:38 PM

Q: is there some support for terms like “Nicht-Tumorpatienten” in order to be found when I search for “nicht tumorpatienten”

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

05:40 PM

You want to add hyphen to the token separators config when you create the collection

05:40

Jason

05:40 PM

That will make those get indexed as two words

A

05:42 PM

but then searching for “Nicht-Tumorpatienten” would result in no hits, correct?

Jason

06:05 PM

That setting will apply both during search time and indexing time

Typesense

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

Indexed 3011 threads (79% resolved)

Join Our Community

Similar Threads

Dealing with Hyphenated Search Results in Typesense

Martin faced issues with hyphenated search results in Typesense. Jainil suggested using `token_separators` to index such search terms separately.

Handling Infix Search in Typesense

Lalit asked about handling infix search in Typesense. Dima suggested adding '-' to token separators. Lalit anticipated more special cases. Kishore Nallan argued infix search might be CPU intensive and might be better for handling initial typos.

3mo

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.

19mo