..@thetaphi.de > -Original
> Message- > From: alex stark > Sent: Thursday,
> August 9, 2018 9:12 AM > To: java-user >
> Cc: java-user@lucene.apache.org > Subject: Re: Legacy filter strategy in
> Lucene 6.0 > > Thanks Adrien, I want to filter out docs base on
Schindler Achterdiek 19, D-28357 Bremen http://www.thetaphi.de eMail:
u...@thetaphi.de > -Original Message- > From: alex stark
> Sent: Thursday, August 9, 2018 9:12 AM > To: java-user
> Cc: java-user@lucene.apache.org > Subject: Re:
Legacy filter strategy in Lucene 6
9, D-28357 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: alex stark
> Sent: Thursday, August 9, 2018 9:12 AM
> To: java-user
> Cc: java-user@lucene.apache.org
> Subject: Re: Legacy filter strategy in Lucene 6.0
>
> Thanks Adrien,
Thanks Adrien, I want to filter out docs base on conditions which stored in doc
values (those conditions are unselective ranges which is not appropriate to put
into reverse index), so I plan to use some selective term conditions to do
first round search and then filter in second phase. I see th
Hi Alex,
These strategies still exist internally, but BooleanQuery decides which one
to use automatically based on the cost API (cheaper clauses run first) and
whether sub clauses produce bitset-based or postings-based iterators.
Le mer. 8 août 2018 à 09:46, alex stark a écrit :
> As FilteredQu
