We used to run that way, with an exact search first, then a broad search if there were no results.
It has an interesting failure mode. If the user misspells a word (about 10% of queries do), and the misspelling matches a misspelled document, then you are stuck. It will never show the correctly-spelled document. For the very popular book Campbell Biology, if you searched for “cambell”, it would show a book with Greek plays and one misspelled author. Oops. We integrated fuzzy search into edismax. With that, we get the popular book for misspelled queries. You can find that patch in SOLR-629. I first implemented it for Solr 1.3, and I’ve been updating it for years. Very useful, especially with the fast fuzzy introduced in 4.x. https://issues.apache.org/jira/browse/SOLR-629 <https://issues.apache.org/jira/browse/SOLR-629> wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Dec 5, 2016, at 9:08 AM, Charlie Hull <char...@flax.co.uk> wrote: > > On 05/12/2016 09:18, Andrea Gazzarini wrote: >> Hi guys, >> I developed this handler [1] while doing some work on a Magento -> Solr >> project. >> >> If someone is interested (this is a post [2] where I briefly explain the >> goal), or wants to contribute with some idea / improvement, feel free to >> give me a shout or a feedback. >> >> Best, >> Andrea >> >> [1] https://github.com/agazzarini/invisible-queries-request-handler >> [2] >> https://andreagazzarini.blogspot.it/2016/12/composing-and-reusing-request-handlers.html >> > We like this idea: we've seen plenty of systems where it's hard to change > what the container system using Solr is doing (e.g. Hybris, Drupal...) so to > be able to run multiple searches in Solr itself is very useful. Nice one! > > Charlie > > > -- > Charlie Hull > Flax - Open Source Enterprise Search > > tel/fax: +44 (0)8700 118334 > mobile: +44 (0)7767 825828 > web: www.flax.co.uk >
