My guess is that it would depend on the number of docs in the index,
how many match, how complex your query is, probably other things.
If q is complex the MatchAllDocs variant might be well be quicker but
if q is simple I wouldn't like to guess. I'm not sure there is any
point in passing the fil
would be the most
performing:
searcher.search( new MatchAllDocsQuery(), filter, max )
or
searcher.search( new ConstantScoreQuery( q ), filter, max )
or
something completely different?
TIA
--
View this message in context:
http://lucene.472066.n3.nabble.com/Reusing-a-CachingWrapperF
-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Konstantyn Smirnov [mailto:inject...@yahoo.com]
> Sent: Monday, July 25, 2011 4:16 PM
> To: java-user@lucene.apache.org
> Subject: RE: Reusing a CachingWrapperFilter
>
>
core, does it?
Can I reuse the thcc instance in the loop?
TIA
--
View this message in context:
http://lucene.472066.n3.nabble.com/Reusing-a-CachingWrapperFilter-tp3196928p3197593.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
--
://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Konstantyn Smirnov [mailto:inject...@yahoo.com]
> Sent: Monday, July 25, 2011 11:08 AM
> To: java-user@lucene.apache.org
> Subject: Reusing a CachingWrapperFilter
>
> Hi all!
>
> are there any limitations
combined
with the new one inside the BooleanFilter like that?
Or maybe should I use searcher.search( query, filter, ... ).totalCount
instead of catFilter.getDocIdSet( indexReader ).cardinality()?
TIA
Konstantyn
--
View this message in context:
http://lucene.472066.n3.nabble.com/Reusing-a
