Also Solr simplifies the process of implementing the client side interface. You can use the same indices with clients written in any programming language.
The client side could be in virtually any programming language of your choosing. If you were to work directly with Lucene, that would not be the case. On Wed, Sep 16, 2009 at 9:49 AM, Israel Ekpo <israele...@gmail.com> wrote: > Comparing Solr to Lucene is not exactly an apples-to-apples comparison. > > Solr is a superset of Lucene. It uses the Lucene engine to index and > process requests for data retrieval. > > Start here first : * > http://lucene.apache.org/solr/features.html#Solr+Uses+the+Lucene+Search+Library+and+Extends+it > !* > > It would be unfair to compare to the Apache webserver to a cgi scripting > interface. > > The apache webserver is just the container through with the webrowser > interacts with the CGI scripts. > > This is very similar to how Solr is related to Lucene. > > > On Wed, Sep 16, 2009 at 9:26 AM, balaji.a <reachbalaj...@gmail.com> wrote: > >> >> Hi All, >> I am aware that Solr internally uses Lucene for search and indexing. But >> it would be helpful if anybody explains about Solr features that is not >> provided by Lucene. >> >> Thanks, >> Balaji. >> -- >> View this message in context: >> http://www.nabble.com/When-to-use-Solr-over-Lucene-tp25472354p25472354.html >> Sent from the Solr - User mailing list archive at Nabble.com. >> >> > > > -- > "Good Enough" is not good enough. > To give anything less than your best is to sacrifice the gift. > Quality First. Measure Twice. Cut Once. > -- "Good Enough" is not good enough. To give anything less than your best is to sacrifice the gift. Quality First. Measure Twice. Cut Once.
