Thanks Ard. I think option 2 is good. I will try this.
On 7/13/07, Ard Schrijvers <[EMAIL PROTECTED]> wrote:
The SearchClient is obviously not aware of a changing index, so doesn't
know when it has to be reopened.
You can at least do the following:
1) you periodically check for the index fold
The SearchClient is obviously not aware of a changing index, so doesn't know
when it has to be reopened.
You can at least do the following:
1) you periodically check for the index folder wether its timestamp did change
(or if this stays the same, do it with the files in it) --> if changed, reo
With local indices, it is enough to reopen the IndexSearcher by calling
close() and then renew the IndexSearcher object. How about RemoteSearchers?
Is it necessary to re-initialize remote search server?
--jaf
On 7/12/07, Erick Erickson <[EMAIL PROTECTED]> wrote:
In general, searchers cannot s
In general, searchers cannot see changes to an index with out restarting,
so I suspect that the answer is "no". This is entirely independent of
remote,
parallel, etc.
Erick
On 7/12/07, Sonu SR <[EMAIL PROTECTED]> wrote:
Hi,
I have SearchServer and SearchClient programs. The SearchServer
u
Hi,
I have SearchServer and SearchClient programs. The SearchServer
using RemoteSearchable
for binding the indices in servers . The SearchClient using
ParallelMultiSearcher for searching the indices. The problem is that I have
to restart the search servers for reflecting the index change in se
