We have no problem at all searching while indexing or optimizing.
The only problem we had was on the IndexReader; the reader has visibility only on the documents available on the index when it is first loaded. Thus you have to define a policy to drop and recreate the reader periodically.
This because I think (if I have understood it well) Lucene handles the duplication of the index on its own, if there are active readers while it update and index.
Hope this helps.
Giulio Cesare Solaroli
On Tuesday, Oct 14, 2003, at 18:27 Europe/Rome, Dror Matalon wrote:
Hi Folks,
Is there a recommended strategy to deal with allowing to search an index
that is updated continuously?
One idea that I thought of is to have two indexes one for searching and
one for indexing. Periodically I would copy new files from the indexed
index to the search index and then I would stop writing to the original
index and then call optimize on both of them. The main advantage to this
is that I would only be copying the new data over. Since our index files
are over 1 gig, this is important because I wouldn't want to suspend
searches for too long.
The only problem is that I suspect that while I run the optimize() the index is unavailable for searches.
Any better strategies for this?
This is all on a Unix system.
-- Dror Matalon Zapatec Inc 1700 MLK Way Berkeley, CA 94709 http://www.zapatec.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
