#community-help

Switching from Meilisearch to Typesense: Query Matching Discussion

TLDR Arad asks about migrating from Meilisearch to Typesense due to matching issues. Kishore Nallan confirms Typesense matches the example correctly. John talks about typo tolerance settings, which Arad refutes as the root cause.

2mo

Join the chat

Oct 03, 2023 (2 months ago)

Photo of md5-c2105be1c75ca77ae57ab06abafe105c

Arad

03:52 PM

Hey there. Quick question: We're currently using Meilisearch but are thinking about migrating to Typesense primarily because Meilisearch has this major problem.
I just wanted to ask whether Typesense is smarter in this regard, or does it also behave like Meilisearch when it comes to scenarios like the one described in the issue?

In short, Meilisearch doesn't match a document that has a field with the value Apple MacBook with the query appl macbook, which is very strange.
You can check out the issue I linked to (it's not long) for more information.

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

04:03 PM

Hi Arad 👋

Yes that should work. I just tried here, and you can see it working fine: https://gist.github.com/kishorenc/126c5529c9c65df7133ec087928eaada

Arad

04:28 PM

Kishore Nallan Thank you very much!

Oct 04, 2023 (2 months ago)

Photo of md5-21545f1facb7836c149bc4c70752bd2b

John

03:29 PM

I haven't tried Meilisearch recently, but wouldn't your issue be resolved by adjusting the minimum word length for typo tolerance? In Typesense it defaults to min_len_1typo=4 whereas the default seems to be 5 in Meilisearch, and that might explain this particular issue.

03:30

John

03:30 PM

(this is just a guess because appl is exactly 4 characters 🙂)

Arad

03:39 PM

John Actually I did try that and unfortunately even though it might solve this particular example, there are other similar examples where the uni-directional matching strategy (which I explained in the issue I linked to) becomes problematic again, so the typo-tolerance settings are not actually the root cause of the problem.

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

Transitioning from Meilisearch to Typesense - Questions and Suggestions

Al is moving from Meilisearch to Typesense and asked for similar matching information features. They also proposed adding daily backups. Kishore Nallan helped them find a workaround, while noting expected complexities, and agreed to include their suggestions in their backlog.

33mo

Inconsistent Results from Filter_by Function in Typesense

Md.Riad was getting varying product results using Typesense's filter_by function. John suggested it might be a typo-correction issue while Kishore Nallan advised increasing the max_candidates parameter.

2mo

Typesense Bug Fix with `canceled_at` Field and Upgrade Concerns

Mateo reported an issue regarding the treatment of an optional field by Typesense which was confirmed a bug by Jason. After trying an upgrade, an error arose. Jason explained the bug was due to a recent change and proceeded to downgrade their version. Future upgrade protocols were discussed.

10mo