#community-help

Typesense Search Issue for Two Terms

TLDR Andreas had a question about a search problem in Typesense. Kishore Nallan suggested it should be fixed in version 0.23. However, Andreas confirmed the issue persists in 0.23.1.

14mo

Join the chat

Oct 12, 2022 (14 months ago)

Photo of md5-2f94b63d050dad6ced4a85316a658c61

Andreas

11:56 AM

Hi there, shouldn’t a search for two terms like in this example act like an OR search and produce identical results?

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

12:06 PM

Yes, what version of Typesense is this on?

Andreas

12:35 PM

0.22.1

Kishore Nallan

12:37 PM

Gotcha, this behavior should be much better in 0.23 and recent RCs. Earlier, cross field matches of tokens in the query across different fields were a bit of a brute force so this could have happened. It should be fixed in 0.23+

Andreas

12:37 PM

also happens with 0.23.1

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

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.

21mo

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.

Issue with Typesense Search and Special Characters

gab faced an issue with Typesense when searching with special characters. Jason and Kishore Nallan provided support and identified the issue as a bug. The problem was resolved after upgrading to `0.25.0.rc44`.

5mo