Any reasons to prefer Solr over elastic-search?
No. It'd be like preferring memcache over redis. You'll find warriors in both camps, but most people have forgotten there was a debate.
Major Changes from Solr 4 to Solr 5
11–20 of 47 posts
Re: Major Changes from Solr 4 to Solr 5
#12[deleted]
Re: Major Changes from Solr 4 to Solr 5
#13Any reasons to prefer Solr over elastic-search?
Search-wise? You're ending up at Lucene either way.
Scaling-wise? Distributed Elasticsearch doesn't have a Zookeeper dependency, which is nice. But Solr has more sharding flexibility and partition tolerance.
Like everything else, depends on your needs.
Re: Major Changes from Solr 4 to Solr 5
#14At my company, we've been beating our heads to the wall[0] in getting multi-term synonyms to work correctly in SOLR. e.g.
fruit extractor => fruit juicer, citrus juicer
[0] - http://opensourceconnections.com/blog/2013/10/27/why-is-mult...
Re: Major Changes from Solr 4 to Solr 5
#15Any reasons to prefer Solr over elastic-search?
Search-wise? You're ending up at Lucene either way. Scaling-wise? Distributed Elasticsearch doesn't have a Zookeeper dependency, which is nice. But Solr has more sharding flexibility and partition tolerance. Like everything else, depends on your needs.
> partition tolerance
Yes, see [1] and [2] for a comparison between Solr and Elasticsearch. I should mention also that ES are working on the partition tolerance issue as described in [3]. I am currently using 1.4.3 and am wondering if anything was addressed in 1.4 for resiliency.
[1] http://lucidworks.com/blog/call-maybe-solrcloud-jepsen-flaky... [2] https://aphyr.com/posts/317-call-me-maybe-elasticsearch [3] http://www.elasticsearch.org/blog/resiliency-elasticsearch/
Re: Major Changes from Solr 4 to Solr 5
#16Earlier quoted context omitted.
Well, regardless of whether it's web-facing or not, it's not unreasonable to want to limit the access to its admin panel (e.g. in a big company with different teams). I agree however that SOLR is best off doing one thing well, web page security can be implemented e.g. by Apache.
So limit it to only whitelisted IPs. That's why you have sysadmins.
Or use Nginx as a proxy, or something. It's frustrating, but I can see the argument for Solr to just delegate this kind of task to other projects that do it better.
Re: Major Changes from Solr 4 to Solr 5
#17Any reasons to prefer Solr over elastic-search?
For your use case set up both and then do some testing.
Speaking for myself I did that and found that SOLR was a lot more performant. I needed a high-traffic solution without a bunch of servers.
I find that ES tries to do too much with all the dashboards and monitoring etc.
SOLR keeps it simple and thereby does not incur the performance penalty.
Also when an ES cluster goes south (cluster health "yellow" or "red") it seemed like a pain to troubleshoot and determine the real reason WHY. SOLR seems more durable and when something needs investigation you get a clear message in the log.
If you are starting something new and just don't know your traffic requirements and are scared of it "going viral" like a hot new mobile game ES may work for you though. The one thing it excels at is adding more ES servers to the cluster quickly. So if you need more servers ASAP and don't care about the cost ES has that covered.
Re: Major Changes from Solr 4 to Solr 5
#18At my company, we've been beating our heads to the wall[0] in getting multi-term synonyms to work correctly in SOLR. e.g. fruit extractor => fruit juicer, citrus juicer Does anyone experienced enough have a clue if SOLR 5 can help with that? [0] - http://opensourceconnections.com/blog/2013/10/27/why-is-mult...
This guy fixed it for 3 and 4
https://github.com/healthonnet/hon-lucene-synonyms
The Solr guys don't give a flying F about this issue though
Re: Major Changes from Solr 4 to Solr 5
#19Does Solr 5.0 support password-protecting the admin interface yet without spending hours trying to wrangle custom XML files? It seems like a pretty basic requirement for a web-based application. I've tried things like this http://community.zimbra.com/documentation/w/documentation/se... repeatedly. They never seem to work right.
Disclaimer: I work at Cloudera on Solr and related technologies.
I don't think there's anything out of the box in Solr 5.0 that changes that. SOLR-4470[0] should be able to do that, but it hasn't been committed. Apache Sentry[1] adds role based access control to Solr, but it's only been tested up to Solr 4.10 and with kerberos (not basic password protection). It comes nicely integrated out-of-the-box with Solr as part of Cloudera Search[2]; otherwise, you'll have to do some manual setup to get it to work.
[0] https://issues.apache.org/jira/browse/SOLR-4470 [1] https://sentry.incubator.apache.org/ [2] http://www.cloudera.com/content/cloudera/en/products-and-ser...
Re: Major Changes from Solr 4 to Solr 5
#20Any reasons to prefer Solr over elastic-search?
Solr is backed by the Apache community while ES is backed by a private entity. Is that a good reason?
I don't know what you mean when you say backed by the Apache Community, but Elasticsearch is also an open source, apache-licensed project that has a commercial, private counterpart. I think every major open source project has this now (Hadoop has Cloudera/Hortonworks/MapR, Spark has databricks).