Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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_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



The 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/, it's described as an "Elasticsearch alternative," so the confusion is probably just here on HN :)


I agree, only reason I read the project readme was to see the drop-in explainer.

Very misleading title


cc klaussilveira


Well, it says right there in the GitHub About section: "Drop-in replacement for E in the ELK stack".




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: