What is the difference between solr and lucene

Elasticsearch is technically open source but not fully. All contributors have access to the source code, and users can make changes and contribute them. But final changes get confirmation from employees of Elastic the company that runs Elasticsearch and other software. Therefore, Elasticsearch is driven more by a single company rather than a whole community. Going back to the mids, Solr contributors and committers span multiple organizations while Elasticsearch committers are from Elastic only.

These members also invest in the platform by contributing throughout the entire development and engineering process. This has changed drastically in the last five years. It is by far the most popular open source time-series database and search engine in DevOps at the beginning of the s. Historically, both have had great user bases as well as rich developer communities, but Elasticsearch has overtaken Solr. Solr has been around for a much longer period of time, but its ecosystem has stagnated even after having a well-developed and has a larger user base.

On this, Elasticsearch documentation wins. Over the last four years, Elasticsearch enhanced its documentation to go beyond organization. Additionally, it offers good examples and clear configuration instructions. In comparison, Solr documentation is lacking. It used to be the other way around: Solr was a very well-documented product with clear examples and contexts for API use cases. However, its documentation maintenance has fallen behind, with gaps noted by many users.

Selecting a clear winner between these two technologies requires a complete understanding of the use cases they support, their feature sets, the scaling options they offer, and their ease of maintenance. Both of these technologies are quite easy to begin working with. Solr offers great functionalities in the field of information retrieval, but Elasticsearch is much easier to take into production and scale. When choosing your tool, make sure to look at your requirements and make the best selection for your specific use case.

What are the implication of Elastic coming from a single company clear vs being community driven? ElasticSearch lacks a web crawler. Sure, people throw around Nutch, Scrapy and others, but no-one of them have got them to work with the latest version of ES.

Elastic has missed the boat to win over a lot more GSA users with this fundamental miss, which makes me concerned for their strategic vision and longevity. Platform Overview. Features Alerts. Fully-Managed ELK. About us. There are people, falling under ' have to use Lucene ' camp, but still prefer Solr to plain Lucene as it's easy to use. However, they never restrain themselves from customizing Solr to the maximum extent.

Lucene is a low level Java library with ports to. NET, etc. Solr has also got some extra features on top e. A simple way to conceptualize the relationship between Solr and Lucene is that of a car and its engine.

You can't drive an engine, but you can drive a car. Similarly, Lucene is a programmatic library which you can't use as-is, whereas Solr is a complete application which you can use out-of-box.

Source: Lucene-vs-solr - Lucene Tutorial. Reference article : Enterprise search. You just need to know how to drive car SOLR and also need to know few things of engine Lucene in case if there will be any issue in your car engine. You can imagine it the following way - Apache Lucene is the library that is used internally by the Apache Solr. It is written in Java and provides amazing full-text search and indexing capabilities.

It can analyze a large number of languages from all over the world and prepare the text in such languages to efficient and fast search and analysis. Lucene is a library - you could use it directly in your application and implement everything yourself, but the Apache Solr provides a lot out of the box.

You can control the search engines using the API, create distributed environments and automatically distribute the data across multiple nodes and many, many more. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Difference between solr and lucene Ask Question.

Asked 8 years, 7 months ago. Apache Solr: An open source search platform. It uses the tools you use to make application building a snap. It is built on the battle-tested Apache Zookeeper, it makes it easy to scale up and down; Lucene: A high-performance, full-featured text search engine library written entirely in Java.

Get Advice. Follow I use this. Seamlessly search your MongoDB Atlas clusters. Apache Solr vs Lucene: What are the differences? Apache Solr and Lucene can be categorized as "Search Engines" tools.

Net, Common. Logging for logging, and Remotion. Linq for helping with LINQ query parsing and translation. I originally evaluated the possibility of contributing to LINQ to Lucene, but found that the tight coupling to EF and some other assumptions made the library inappropriate for my needs.

Linq does not have extension methods for every query that Lucene. Net supports natively. However, it does provide an escape hatch where you can pass in your own Query :. If the field is indexed as a keyword, exact matching takes effect. Thanks for your feedback! I write this as answer since it is too long otherwise.

I actually got the same response from the mailing list:. Is this normal behaviour? I thought the existing document should be updated instead of generating a new document with same id. Before executing the query on the server, the client would not know about what you have set on the server side, right?