I will try to take a crack at these, but not sure I know exactly what
you are looking for, so maybe others can chime in too.
At any rate, MultiSearcher has been around a lot longer (2001 versus
2004, or at least that is what the changelog seems to indicate) and
it works over Searchables, including RemoteSearchable. So you could
use it to combine results from remote searches as well, MultiReader
can only work over IndexReaders and I am not aware of any way that it
can do remote index reading, so there are different viable use cases
for the two.
On Apr 17, 2007, at 2:48 PM, Kirk Roberts wrote:
I've been on this list long enough to have a vast repository of
information about using a MultiSearcher versus an IndexSearcher
that works on a MultiReader. However, after looking through
several hundred list postings, I could not find what I was looking
for. So if there is a posting or thread (or website, for that
matter) that answers all my questions, please direct me there and,
if so, I apologize in advance.
From what I have read, people seem to suggest using an
IndexSearcher initialized with a MultiReader over the use of a
MultiSearcher. This begs 2 questions:
1. Under what conditions is a MultiSearcher necessary/optimal?
2. Why doesn't the MultiReader implement the rather nice methods
that the MultiSearcher has (I'm thinking specifically of subSearcher
(int) and subDoc(int))?
I suppose subDoc might make sense, but subSearcher does not for a
Reader. Perhaps the private readerIndex() method on MultiReader is
something you are interested in? Is that getting at what you want?
Maybe you can submit a patch that makes readerIndex public if that is
what you are interested in?
Hope this helps,
Grant
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
