4 ms·
I was searching for a Meilisearch alternative (which sends out telemetry by default) and found Tantivy. It's more of a search engine builder, but the setup loo
by kaathewise 2y ago
I was searching for a Meilisearch alternative (which sends out telemetry
by default) and found Tantivy. It's more of a search engine builder,
but the setup looks pretty simple [0].
[0]: https://github.com/quickwit-oss/tantivy-cli https://github.com/quickwit-oss/tantivy-cli
- OtomotO 2y agoHm, I am interested, but I would love to use it as a rust lib and just have rust types instead of some json config... The java sdk of meilisearch was also nice, same: no need for a cli and manual configuration. I just pointed it to a db entity and indexed whole tables... Would love that for tantivy
- PSeitz 2y ago> Hm, I am interested, but I would love to use it as a rust lib and just have rust types instead of some json config... Yes that's how you use tantivy normally, not sure which json config you mean. tantivy-cli is more like a showcase, https://github.com/quickwit-oss/tantivy https://github.com/quickwit-oss/tantivy is the actual project.
- OtomotO 2y agoYes, and there is https://tantivy-search.github.io/examples/basic_search.html https://tantivy-search.github.io/examples/basic_search.html But instead of this, I would prefer some way to just hand it JSON and for it to just index all the fields... for comparison, this is my meilisearch SDK code: fun createCustomers() { val client = Client(Config("http://localhost:7700", "password")) val index = client.index("customers") val customers = transaction { val customers = Customer.all() val json = customers.map { CustomerJson.from(it) } Json.encodeToString(ListSerializer(CustomerJson.serializer()), json) } index.addDocuments(customers, "id") }
- banish-m4 2y agoThat's a petty objection to usable interactive search when it's easy to opt-out by adding a single command line argument.
- Nathanba 2y agoalso meilsearch is more like quickwit, their distributed offering but quickwit is AGPL
- PSeitz 2y agoThey serve quite different use cases. quickwit was built to handle extremely large data volumes, you can ingest and search TB and PB of logs. meilisearches indexing doesn't scale as it will become slower the more data you have, e.g. I failed to ingest 7GB of data.
- qdequelen 2y agoHey PSeitz, Meilisearch CEO here. Sorry to hear that you failed to index a low volume of data. When did you last try Meilisearch? We have made significant improvements in the indexing speed. We have a customer with hundreds of gigabytes of raw data on our cloud, and it scales amazingly well. https://x.com/Kerollmops/status/1772575242885484864 https://x.com/Kerollmops/status/1772575242885484864
- banish-m4 2y agoFrankly, I'm okay with Meillisearch for instant search because y'all are clear about analytics choices, offer understandable FOSS Rust, and have a non-AGPL license. If/when we make some money, I'm in favor of $upporting and consulting of tools used to keep them alive out of self-interest.
- soulofmischief 2y agoOP is entitled to make political choices when selecting software. Some of us have specific principles of which things like opt-out telemetry might run afoul. OP will choose their software, I choose mine and you choose yours; none of us need to call each other petty or otherwise cast such negative judgement; a free market is a free market.
- ukuina 2y agoQuickWit also sends telemetry by default: https://quickwit.io/docs/telemetry https://quickwit.io/docs/telemetry