Hacker News new | comments | show | ask | jobs | submit login

Well after talking to some of their tech guys we determined that we have different definitions for the work "fixed".

Such as?

Such as disallowing configuration they do not like, having memory/resource leaks that they cannot find the root cause for and few other things I forgot already. G1GC is disallowed because they had a data corruption bug with it. This is few months back, they might changed some it already. The question for me is what do I get using ES over Solr? If Solr's features are enough for our use cases should I even try ES?

Here is their resiliency status: https://www.elastic.co/guide/en/elasticsearch/resiliency/cur...

It depends on your use case. If you are already familiar with Solr and it is good enough for your use case, then use it. Solr and ES are about the same feature-wise. Scaling is easier for ES because it is built-in. Here is a good comparison of their APIs.

part 1: http://opensourceconnections.com/blog/2015/12/15/solr-vs-ela...

part 2: http://opensourceconnections.com/blog/2016/01/22/solr-vs-ela...

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact