lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ian Lea <>
Subject Re: Filtering top hits based on stored field? And Lucene 1.x -> 3.x for Dummies
Date Fri, 25 Jan 2013 20:31:42 GMT
On the specific question, calling doc() is still expensive.  You could
look at the FieldCache or the new DocValues stuff. See
for info on the latter.

On the general question, much of your lucene knowledge will still be
relevant.  There'll be some new stuff you've never heard of, and loads
of changes behind the scenes you may be able to ignore, but the basic
concepts and techniques haven't changed that much.  I suggest reading
the Changes doc from 4.1.


On Fri, Jan 25, 2013 at 4:15 PM, Andrew Gilmartin
<> wrote:
> I have been using Lucene since 1.x days, but that also means I am carrying
> around some information that is no longer relevant and using techniques that
> are antiquated. I am currently using 3.0 but I am sure I am using it in 1.0
> fashion. I have two questions -- one general and one specific.
> The specific question is how, in Lucene 3.x, can I filter the
> results based on stored fields within candidate hits?
> It is not acceptable to perform the filter post search as now my hits list
> is too short. In the past calling doc() during a search (with my own
> collector) resulted in a severe performance hit. Is that still the case? If
> not, great I will just do that. If it still is, how would you suggest I
> implement the filtering?
> The general question is how can I best come up to speed with Lucene 3.6
> and/or 4.0? Should I just consider my existing knowledge redundant and learn
> Lucene and Solr anew? Or are there documents that can better direct my
> re-education?
> -- Andrew
> --
> Andrew Gilmartin
> 401-441-2062
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message