Choosing a stand-alone full-text search server: Sphinx or SOLR? [closed]

问题

I'm looking for a stand-alone full-text search server with the following properties:

Must operate as a stand-alone server that can serve search requests from multiple clients
Must be able to do "bulk indexing" by indexing the result of an SQL query: say "SELECT id, text_to_index FROM documents;"
Must be free software and must run on Linux with MySQL as the database
Must be fast (rules out MySQL's internal full-text search)

The alternatives I've found that have these properties are:

Solr (based on Lucene)
ElasticSearch (also based on Lucene)
Sphinx

My questions:

How do they compare?
Have I missed any alternatives?
I know that each use case is different, but are there certain cases where I would definitely not want to use a certain package?

回答1:

I've been using Solr successfully for almost 2 years now, and have never used Sphinx, so I'm obviously biased. However, I'll try to keep it objective by quoting the docs or other people. I'll also take patches to my answer :-)

Similarities:

Both Solr and Sphinx satisfy all of your requirements. They're fast and designed to index and search large bodies of data efficiently.
Both have a long list of high-traffic sites using them (Solr, Sphinx)
Both offer commercial support. (Solr, Sphinx)
Both offer client API bindings for several platforms/languages (Sphinx, Solr)
Both can be distributed to increase speed and capacity (Sphinx, Solr)

Here are some differences:

Solr, being an Apache project, is obviously Apache2-licensed. Sphinx is GPLv2. This means that if you ever need to embed or extend (not just "use") Sphinx in a commercial application, you'll have to buy a commercial license (rationale)
Solr is easily embeddable in Java applications.
Solr is built on top of Lucene, which is a proven technology over 8 years old with a huge user base (this is only a small part). Whenever Lucene gets a new feature or speedup, Solr gets it too. Many of the devs committing to Solr are also Lucene committers.
Sphinx integrates more tightly with RDBMSs, especially MySQL.
Solr can be integrated with Hadoop to build distributed applications
Solr can be integrated with Nutch to quickly build a fully-fledged web search engine with crawler.
Solr can index proprietary formats like Microsoft Word, PDF, etc. Sphinx can't.
Solr comes with a spell-checker out of the box.
Solr comes with facet support out of the box. Faceting in Sphinx takes more work.
Sphinx doesn't allow partial index updates for field data.
In Sphinx, all document ids must be unique unsigned non-zero integer numbers. Solr doesn't even require an unique key for many operations, and unique keys can be either integers or strings.
Solr supports field collapsing (currently as an additional patch only) to avoid duplicating similar results. Sphinx doesn't seem to provide any feature like this.
While Sphinx is designed to only retrieve document ids, in Solr you can directly get whole documents with pretty much any kind of data, making it more independent of any external data store and it saves the extra roundtrip.
Solr, except when used embedded, runs in a Java web container such as Tomcat or Jetty, which require additional specific configuration and tuning (or you can use the included Jetty and just launch it with java -jar start.jar). Sphinx has no additional configuration.

回答2:

Unless you need to extend the search functionality in any proprietary way, Sphinx is your best bet.

Sphinx advantages:

Development and setup is faster
Much better (and faster) aggregation. This was the killer feature for us.
Not XML. This is what ultimately ruled out Solr for us. We had to return rather large result sets (think hundreds of results) and then aggregate them ourselves since Solr aggregation was lacking. The amount of time to serialize to and from XML just absolutely killed performance. For small results sets though, it was perfectly fine.
Best documentation I've seen in an open source app

Solr advantages:

Can be extended.
Can hit it directly from a web app, i.e., you can have autocomplete-like searches hit the Solr server directly via AJAX.

回答3:

Note: There are many users with the same question in mind.

So, to answer to the point:

Which and why?

Use Solr if you intend to use it in your web-app(example-site search engine). It will definitely turn out to be great, thanks to its API. You will definitely need that power for a web-app.
Use Sphinx if you want to search through tons of documents/files real quick. It indexes real fast too. I would recommend not to use it in an app that involves JSON or parsing XML to get the search results. Use it for direct dB searches. It works great on MySQL.

Alternatives

Although these are the giants, there are plenty more. Also, there are those that use these to power their custom frameworks. So, i would say that you really haven't missed any. Although there is one elasticsearch that has a good user base.

回答4:

I have been using Sphinx for almost a year now, and it has been amazing. I can index 1.5 million documents in about a minute on my MacBook, and even quicker on the server. I am also using Sphinx to limit searches to places within specific latitudes & longitudes, and it is very fast. Also, how results are ranked is very tweakable. Easy to install & setup, if you read a tutorial or two. Almost 1.0 status, but their Release Candidates have been rock solid.

回答5:

Lucene / Solr appears to be more featured and with longer years in business and a much stronger user community. imho if you can get past the initial setup issues as some seems to have faced (not we) then I would say Lucene / Solr is your best bet.

来源：https://stackoverflow.com/questions/1284083/choosing-a-stand-alone-full-text-search-server-sphinx-or-solr

标签

mysql

full-text-search

lucene

solr

sphinx