Supermind Search Consulting Blog 
Solr - Elasticsearch - Big Data

SolrCloud search request lifecycle and writing distributed Solr SearchComponents

Posted by Kelvin on 02 Jul 2018 | Tagged as: Lucene / Solr / Elasticsearch / Nutch

Recap To recap, in a previous article, we saw that a SearchComponent comprises of a prepare() and process() method: public class TestSearchComponent extends SearchComponent { @Override public void prepare(ResponseBuilder rb) throws IOException {   }   @Override public void process(ResponseBuilder rb) throws IOException {   } } and that the standalone SolrCloud application flow of […]

Introducing SolrCloud

Posted by Kelvin on 02 Jul 2018 | Tagged as: Lucene / Solr / Elasticsearch / Nutch

In this post, we will examine SolrCloud and examine how it is different from standalone Solr.. Introducing SolrCloud In a standalone Solr installation, the data resides on a single machine and all requests are served from this machine. SolrCloud is the operation mode in Solr where the data resides on multiple machines (known as a […]

Developing a Solr SearchComponent for standalone Solr

Posted by Kelvin on 02 Jul 2018 | Tagged as: Lucene / Solr / Elasticsearch / Nutch

In this article, I discuss SearchComponents briefly, and show how straightforward it is (in non-SolrCloud mode) to develop a custom Solr SearchComponent. In the next articles in the series, we examine the flow of logic in SolrCloud mode, and how you might be able to develop a SolrCloud-compatible SearchComponent. Standalone Solr/non-SolrCloud In standalone Solr mode, […]

Introducing this series on developing Solr SearchComponents

Posted by Kelvin on 01 Jul 2018 | Tagged as: Lucene / Solr / Elasticsearch / Nutch

Solr and Elasticsearch more or less have feature-parity. Elsewhere, I have examined in detail the similarities and differences between Elasticsearch and Solr. One of the major differences between the 2 open-source search products though, is how easy it is to plug custom logic into the search workflow in Solr. In Solr, you do this by […]