Michael McCandless (JIRA) wrote:
However, stepping back, this is poor approach. We should instead be
doing what MultiSearcher does, which is gather top results
per-sub-reader, and then merge-sort the results. At that point, to do
the merge, we only need actual field values for those docs in the top
N.
What if one segment has the 20 best docs and a second segment has only
pretty poor docs - and then various mixes in between. This is how it
works with MultiSearcher right? MultiSearcher has a few aspects I don't
like.
I may not be fully understanding yet though. I have a slow understanding
time and a fast response time. Brilliant combination :) Its like a fish
with feet.
I hope I'll be playing around more with some of these ideas though (free
time is not as plentiful as I would like at the moment). I should have
some better comments to make about it then.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
