On Aug 30, 2008, at 4:43 AM, Karl Wettin wrote:
Can you tell us a bit more about what you custom query does? Perhaps
you can build the "candidate filter" and reuse it over and over again?
I cannot reuse it. The candidate filter would be constructed by first
running a boolean query with a number of SHOULD clauses. So then I
know what docs atleast contain the terms I'm looking for. Once I have
this set, I will look at the ordering of the matches (it's a bit more
sophisticated than just a phrase query) and find the final matches.
Since my boolean clauses are different for each query I can't reuse
the filter.
--
Matt
Hi all,
I am working on implementing a new Query, Weight and Scorer that is
expensive to run. I'd like to limit the number of documents I run
this query on by first building a candidate set of documents with a
boolean query. Once I have that candidate set, I was hoping I could
build a filter off of it, and issue that along with my expensive
query. However, after reading the code I see that filtering is done
during the search, and not before hand. So my initial boolean query
won't help in limiting the number of documents scored by my
expensive query.
Has anyone done any work into restricting the set of docs that a
query operates on?
Or should I just implement something myself in a custom scorer?
Thanks in advance,
--
Matt Ronge
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
