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.
Oct 03, 2023 (2 months ago)
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 MacBookwith the query
appl macbook, which is very strange.
You can check out the issue I linked to (it's not long) for more information.
Kishore Nallan04:03 PM
Yes that should work. I just tried here, and you can see it working fine: https://gist.github.com/kishorenc/126c5529c9c65df7133ec087928eaada
Oct 04, 2023 (2 months ago)
min_len_1typo=4whereas the default seems to be 5 in Meilisearch, and that might explain this particular issue.
Indexed 3011 threads (79% resolved)
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.
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.
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.