The simplese way is to create indexsearcher instance for each searching
request
or create indexsearcher for each index folder (such as indexX, indexY,...),
then write a function to choose correct indexsearcher for related searching
request...
On 4/12/06, wenjie zheng <[EMAIL PROTECTED]> wrote
, April 12, 2006 10:09 PM
To: java-dev@lucene.apache.org
Subject: Re: Question about RemoteSearchable, RMI and queries in
parallel
Thanks for your reply.
I think I didn't address the problem very clear. Let me rephrase it.
There is no such problem if everything is local, literaly we
Thanks for your reply.
I think I didn't address the problem very clear. Let me rephrase it.
There is no such problem if everything is local, literaly we can new as many
IndexSearchers as we need.
However given the fact that there is only one RemoteSearchable instance
running on Server A, how can I
I think you may need a much more advanced design - with change detection,
parallel query execution, and index modification.
A lot of it depends on you semantics of a search - does it mean at the
results are 'almost right' at a moment in time, or are pending index changes
made first before any quer
