Sphinx in Action: Fuzzy matching and 2nd pass query

This is a post from a series of posts called "Sphinx in Action". See the whole series by clicking here.

Many customers that we have helped with integrating search into their applications wanted their search to be more intelligent than just strictly matching a query with documents.

There are many ways to do this. Sphinx makes it very easy, as fuzzy matching is included out of the box. It consists of two main components:

• Quorum operator:

• Proximity search operator:

Many of our customers like the second pass logic when the first query to Sphinx is strict. If nothing is found or not enough results are returned, the second less strict query is issued. There also may be more advanced logic with 3rd and 4th passes. It just depends on your requirements and whether or not you want your user to at least find something in any case. Or, on the contrary, you can let them find something that exactly matches his query.

Sometimes it makes sense to do it the other way around and make the query stricter. For example, if your default matching strategy is 'any word should match' and your application doesn’t have any extended syntax to allow users to specify the best query themselves, it makes sense to first try the 'all words should match' strategy or even the 'phrase should match'. This might significantly increase the quality of the search.

In some applications it makes sense to parallelize the 1st/2nd pass queries and so on. This can be easily done using Spinx multiquery. The logic here is to do the 2nd pass query beforehand and if nothing is found by the 1st pass query the results will be ready and since the queries were done simultaneously this improves performance. However, this depends on a lot of things. You should be careful, as it can reduce performance sometimes. These things are:

• What hardware are you using? If it's not powerful enough to handle two queries at once or the response time is close to the response is double that of a single query, it makes little sense to use this technique.

• What is your load? If your Sphinx is already heavily loaded, you will get a worse response time.

• What are your statistics? If for 99% of queries the 1st pass the query returns results, there's little point to make the 2nd pass query along with the 1st one, this will just waste resources.

---

Need help with search infrastructure? See how Ivinco's development team can help →

Frequently Asked Questions

How does fuzzy matching work in Sphinx search?

Sphinx provides two built-in fuzzy matching operators. The quorum operator ("word1 word2 word3"/2) requires at least N of the listed words to match. The proximity operator ("word1 word2"~5) finds documents where the words appear within N words of each other. Both operators are available out of the box — no plugins or special configuration needed.

What is the second pass query pattern in Sphinx?

The second pass pattern starts with a strict query (exact phrase match or all-words-required). If the result count is zero or below a threshold, a looser query is issued automatically — for example, switching from phrase match to quorum matching. The logic can extend to 3rd and 4th passes: exact phrase → all words → quorum (2/3) → any word. This balances precision with recall.

When should you use Sphinx multiquery for search passes?

Multiquery sends multiple queries to Sphinx in a single request, executing them in parallel. Use it when your first-pass query has a reasonable chance of returning zero results and the response time for a single query is already near your latency budget. On underpowered hardware or heavily loaded servers, multiquery can increase response time rather than reduce it.

Related Reading

• Sphinx in Action: Autocomplete
• Sphinx in Action: Did you mean ... ?
• Sphinx in Action: How Sphinx handles text during indexing