3 ms·
One should not use "drop-in" when they have their own query language and seemingly input shape for the /search endpoint (which is also different from Elastic, o
by mdaniel 1y ago
One should not use "drop-in" when they have their own query language and seemingly input shape for the /search endpoint (which is also different from Elastic, of course) https://manual.manticoresearch.com/Searching/Full_text_matching/Basic_usage#query_string https://manual.manticoresearch.com/Searching/Full_text_match...
It sounds like they're really targeting the logging search store part of ELK, which can be a perfectly fine objective, but no need to mislead audiences since they will find out and then you've made an enemy
- tbarbugli 1y agoI agree, only reason I read the project readme was to see the drop-in explainer. Very misleading title
- andygeorge 1y agocc klaussilveira
- klaussilveira 1y agoWell, it says right there in the GitHub About section: "Drop-in replacement for E in the ELK stack".
- snikolaev 1y agoThe Manticore Search github repository calls it a "drop-in replacement for E in the ELK stack," not just a replacement for Elasticsearch. On https://manticoresearch.com/ https://manticoresearch.com/, it's described as an "Elasticsearch alternative," so the confusion is probably just here on HN :)