Hi,
We plan to migrate from lucene 5.5 to 6.5. We have been using
DocValuesTermsFilter extensively which was deprecated in Lucene 5.5 and removed
in Lucene 6.0.
The Javadoc specifies to use DocValuesTermsQuery and BoolenaClause.Occur.Filter
instead. However, as per our local tests, the time
and filter then.
Or alternative: Just wrap all filters with ConstantScoreQuery() and add them
to the BooleanClause as before, so all Filters get normal Queries and can
used as your queries before, and leave BooleanFilter away. The only good
thing of BooleanFilter is, that it optimizes the combining
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 filters
about filters and realized that several of
the things we do with queries should probably be done with filters
(queries where the boost was set to 0.0 was the clue). But I'm having
trouble making them work.
Currently, the code that builds the user's query calls several other
classes and asks
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=threadfrom=943115.
It appears that Searchers first compute query results and then filter
those results. Can
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.Query*
