On Mon, Oct 13, 2014 at 11:04 AM, Patrick Schemitz <[email protected]> wrote:
> This Query/Weight/Scorer construct is obviously very costly, so I don't > want it to leapfrog with the other - much faster - filters in the query > (especially when using a high threshold). > It’s leap-frogging with filters? That’s strange; filters should be running first, assuming the default cache=true on them. If for some reason you want to not cache filters or other queries, then you cold have your QueryParser parse those queries as additional parameters, and then construct a FilteredQuery configured with your query and QUERY_FIRST_FILTER_STRATEGY. Cheers, David
