It's ridiculously easy to use and has faceted search for my needs. However, there are some limitations so I have to use it in combination with redis, but the developers have a roadmap to fix these problems.
Synchronising with MeiliSearch is a bit of an effort because of the following limitations:
* When filtering by facet, it doesn't provide count for disjunctive facets
* No sort by
* No where clause (less than 50 for example)
To overcome these problems, I rebuild some parts of the database in redis, use code for filtering and query MeiliSearch multiple times for different facet counts.
Both redis and MeiliSearch are ridiculously fast so the performance loss is negligible, but it makes my code quite complex. As soon as the developers add these missing features, I want to simplify my code and only use redis for query caching. Typesense had some of these limitations too, but I'm not sure if that's still the case.
Hi! MeiliSearch product team here! It's super cool to see your feeback!
Concerning the disjunctive count of the facets, we are thinking about it. It is feasible on the client side by making several requests but we are aware that is it not ideal at all from a developer experience point of view. We are still thinking about the best way to solve that case in one of our future iterations!
The sort feature is coming in v0.22 (string and numeric fields) you will be able to easily configure the balance between exhaustivity and relevancy at index level through the positioning of the ranking rules.
I'm not sure I understand the where clause point so I'd love to hear more details!
Thanks for using us and giving us this kind of feedback :)
Hello, MeiliSearch team here :)
Please, do not hesitate to leave an issue on the Golang repository so we can improve it!
Also, indexing time will be much better with v0.21 planned to be released in a couple of days / weeks. You can test the RC in the meanwhile
I'm also using it for a plant species search on hedira.io, it's been great for the past 6 months or so, even for a more complex faceted search setup. I switched from Algolia (which was easy due to instantsearch integration) and have no regrets.
Yes. Small private project. It's quite fast. It's query interface is REST+JSON and now has an OpenAPIv3 spec; that said some of the query syntax is embedded in strings, so there you are still on your own.
I found the default order of results a bit off. Near-matches were positioned over exact matches.
I'm looking for a fulltext typo-tolerant search tool that integrates well Hasura+PG.
Also interested in the Hasura+PG options. Have you found anything interesting so far? At the moment I’m stringing together a few like clauses, which mostly does for my needs.
I've ran into the same "strip tags" issue. Having used ES before, that does sanitizing and stripping for you, at first I was dissapointed.
However, after thinking about it more, I wrote up this issue[0] with some ideas and thoughts so I could implement it as PR or work around it.
I ended up working around it, because that makes most sense: separation of concerns: meilisearch should indeed not get involved in stripping or fixing HTML as that i) ties Meili to HTML, ii) requires configuration and complexity to allow control and iii) adds features that become security-critical.
Indeed, my solution is to sanitize, clean and strip HTML before sending into the index.