Hi, Since Lucene 6, Filters as a separate class are gone (deprecated in Lucene 5). Every query can now be used as a filter. There are 2 possibilities:
- To apply as a filter next to other scoring queries, use a BooleanQuery with filter clauses (BooleanClause.Occur.FILTER) next to the standard scoring clauses (MUST or SHOULD). The FILTER clauses are standard queries. - To execute a single query without scoring (constant score of 1), use ConstantScoreQuery Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: lukes [mailto:mail2lok...@gmail.com] > Sent: Wednesday, August 10, 2016 1:44 AM > To: general@lucene.apache.org > Subject: Re: Doing Range/NUmber queries > > Hi Michael, > > Do you know, if Filtered Queries are supported in Lucene ? I tried to > find, but couldn't find anything relevant. So i have some queries which i > want to apply as filter, don't want to contribute in the scoring.Would > filter queries speed up the query process ? Can i combine filter and queries > together ? Also during indexing do i need to mention anything special for > fields that can be used in filters ? > > Regards. > > > > -- > View this message in context: http://lucene.472066.n3.nabble.com/Doing- > Range-NUmber-queries-tp4290722p4291058.html > Sent from the Lucene - General mailing list archive at Nabble.com.
