The last few versions of lucene have deprecated several of the
interfaces we were using and this is necessitating a fairly major
upgrade of our code (which hasn't had much done to it for several
years). I'm not complaining; the changes are probably necessary.
In reading LIA2, I've learned abou
I have another newbie question based on a quick glance at some classes
in* org.apache.lucene.search.Query* and at the email thread
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&by=thread&from=943115.
It appears that Searchers first compute query results and then filter
those results. Can
> -Original Message-
> From: Scott Smith [mailto:ssm...@mainstreamdata.com]
> Sent: Wednesday, June 17, 2009 2:15 AM
> To: java-user@lucene.apache.org
> Subject: Queries and Filters
>
> The last few versions of lucene have deprecated several of the
> interfaces w
efore I try the
ConstantScoreQuery solution.
What is the reasoning behind your TermFilter comment?
From: Uwe Schindler [mailto:u...@thetaphi.de]
Sent: Wed 6/17/2009 12:33 AM
To: java-user@lucene.apache.org
Subject: RE: Queries and Filters
If you are only using
The closest thing to that is
http://issues.apache.org/jira/browse/LUCENE-330
-Yonik
Now hiring -- http://forms.cnet.com/slink?231706
On 10/21/05, Rick Hillegas <[EMAIL PROTECTED]> wrote:
>
> I have another newbie question based on a quick glance at some classes
> in* org.apache.lucene.search.Que
