On Fri, Mar 25, 2011 at 2:33 PM, Yonik Seeley <[email protected]> wrote:
>>> Currently, supplying a filter to IndexSearcher.search() assumes that >>> it's cheaper to run than the main query. >> >> Wait, where do we assume that? > > After a match, we always skip on the filter first. Well, we next() on the filter, and advance() on the scorer. >> Also, why stop at 2 filters? Ie I may have 3 filters plus a query to >> AND, and I want to control their order. > > Multiple filters could be combined into a single one via ChainedFilter, etc. True. >> What's the use case behind this...? > > Optimizing cases where filters might be more expensive than the main query ;-) That much I understood ;) But you must have a real use case... that inspired this idea? Where are apps/Solr "typically" using such expensive filters? Mike http://blog.mikemccandless.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
