Powerful, Flexible Search Tool
November 30, 2017
Powerful, Flexible Search Tool
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Apache Solr
- Solved Type-ahead search and provide various faceting options to keep the customer engaged in a Retail domain so that he/she can isolate their products in less than 3 clicks.
- Information Retrieval, Search Engines prototype, Query suggestion Systems
- We are utilizing Solr with our Google Search Appliances for the search functionality within out internal company portal. Solr helps us query other databases for personnel and location information.
- We needed to improve the relevance and performance of our existing search, and by using Solr did both of these with the added benefit of reducing the load on our Oracle Database. We improved our relevance and customers immediately noticed the difference. That was with the 'out-of'the'box' settings, we can see how this can be improved further.
- Solr is a very quick and easy way to search for keywords within a document, the ability to add weightings to search terms to increase the outcome of search relevance gives it great flexibility.
- The customisability of the Solr is so good that anyone can set it up and customise it for his/her needs.
- Solr allows you to build your own custom request handlers and allows you to import data from pretty much any datasource.
- Version 4.3-4.10, the documentation for Solr was very lacking.
- No monitoring for Solr available built-in; have to be dependent on CDH or HDP if you are implementing thru them.
- CPU consumption can be high in some cases.
- Usage of Solr in the browse webpages (apart from Search) has resulted in customer choosing his/her product within 3 clicks by the using of faceting.
- Speed, relevance and efficiency of search results.
- Using Solr for International Markets comes out of box.
Between Solr and ElasticSearch, there is a constant struggle to pick the best one. ElasticSearch is part of ELK and ties in well with LogStash and Kibana which makes it great for logs and big data stuff. Add some logs and see which works best for your particular access methods and queries. They are very similar but elasticsearch is better for REST access.