Add to Jack reply, Solr can also be embed into the application and can run on same process. Solr, the server-I zation of lucene. The line is very blurred and solr is not a very thin wrapper around lucene library.
Most solr features are distinct from lucene like - detailed breakdown of scoring mathematics - text analysis phases - solr adds to lucene's text analysis library and makes it configurable through XML - introduce the notion of a field types - runtime performance stats including cache hit/ miss rate Rgds AJ On 12-Feb-2013, at 22:17, "Jack Krupansky" <j...@basetechnology.com> wrote: > Here's yet another short list of benefits of Solr over Lucene (not that any > of them take away from Lucene since Solr is based on Lucene): > > - Multiple core index - go beyond the limits of a single lucene index > - Support for multi-core or named collections > - richer query parsers (e.g., schema-aware, edismax) > - schema language, including configurable field types and configurable > analyzers > - easier to do per-field/type analysis > - plugin architecture, easily configured and customized > - Generally, develop a search engine without writing any code, and what code > you may write is mostly easily configured plugins > - Editable configuration file rather than hard-coded or app-specific > properties > - Tomcat/Jetty container support enable system administration as corporate IT > ops teams already know it > - Web-based Admin UI, including debugging features such as field/type analysis > - Solr search features are available to any app written in any language, not > just Java. All you need is HTTP access. (Granted, there is SOME support for > Lucene in SOME other languages.) > > In short, if you want to embed search engine capabilities in your Java app, > Lucene is the way to go, but if you want a "web architecture", with the > search engine in a separate process from the "app" in a "multi-tier > architecture", Solr is the way to go. Granted, you could also use > ElasticSearch or roll your own, but Solr basically "runs right out of the > box" with no code development needed to get started and no Java knowledge > needed. > > And to be clear, Solr is not simply an "extension" of Lucene - Solr is a > distinct architectural component that is based on Lucene. In OOP terms, think > of "composition" rather than "derivation". > > -- Jack Krupansky > > -----Original Message----- From: JohnRodey > Sent: Tuesday, February 12, 2013 10:40 AM > To: solr-user@lucene.apache.org > Subject: Benefits of Solr over Lucene? > > I know that Solr web-enables a Lucene index, but I'm trying to figure out > what other things Solr offers over Lucene. On the Solr features list it > says "Solr uses the Lucene search library and extends it!", but what exactly > are the extensions from the list and what did Lucene give you? Also if I > have an index built through Solr is there a non-HTTP way to search that > index? Because solr4j essentially just makes HTTP requests correct? > > Some features Im particularly interested in are: > Geospatial Search > Highlighting > Dynamic Fields > Near Real-Time Indexing > Multiple Search Indices > > Thanks! > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Benefits-of-Solr-over-Lucene-tp4039964.html > Sent from the Solr - User mailing list archive at Nabble.com.
