Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of solrexpert@gmail.com designates
 209.85.215.52 as permitted sender)
MIME-Version: 1.0
Date: Thu, 5 Jun 2014 15:47:20 +0300
Message-ID: 
 <CAHUAEU8KjZYEOQE-CLevJWeJTaRM01EVVTNARYwrypKFKOZxzg@mail.gmail.com>
Subject: OOV queries
From: Dmitry Kan <solrexpert@gmail.com>
To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org>
Content-Type: multipart/alternative; boundary=001a11336b1a4f1c5f04fb1625d8

--001a11336b1a4f1c5f04fb1625d8
Content-Type: text/plain; charset=UTF-8

Hi,

Solr is good at caching: even if first "cold" query takes longer time, the
subsequent one is much quicker, given that it shares the fq's of the first
query.

This is more like an idea question:

what about the out-of-vocabulary (OOV) queries? According to my quick
measurements, they take same amount of time when repeated and return
nothing.

Most of such queries are usually user typos, so I could imagine
implementing a round-trip to the server with an auto-corrected query, if
the first query returned 0 hits. This does not solve the underlining slow 0
hits query though.

Would it make sense to implement an OOV cache to speed things up? Does one
exist already in Lucene / Solr?

-- 
Dmitry Kan
Blog: http://dmitrykan.blogspot.com
Twitter: http://twitter.com/dmitrykan

--001a11336b1a4f1c5f04fb1625d8--