How crazy would it be to refactor HitCollector so it also accept the
matching queries?
Let's ignore my use case (not sure it makes sense yet, it's related to
finding a threadshold between probably interesting and definitly not
interesting results of huge OR-statements, but I really have to try it
out before I can say if it's any good) and just focus on the speed
impact. If I cleared and reused the Collection passed down to the
HitCollector then it shouldn't really slow things down, right? And if
I reused the collections in my TopDocsCollector as low scoring results
was pushed down then it shouldn't have to be expensive there either. Or?
karl
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
