You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by Jayson Minard <ja...@gmail.com> on 2012/01/11 23:33:09 UTC

Re: Caching filters inside bq clauses when using DisMax

This seems wrong still.  It *does* make sense to cache the bq as a filter
since it is re-used every time you issue a new query through dismax.  The
query changes with every q parameter change so that query re-executes but
why do force each bq to execute again?  Keep it, and apply its boost where
it intersects.

--
View this message in context: http://lucene.472066.n3.nabble.com/Caching-filters-inside-bq-clauses-when-using-DisMax-tp2844821p3652081.html
Sent from the Lucene - Java Developer mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org