Hi, As per my understanding of Lucene, I think concurrent search and update to an index should not corrupt the index, given that only a single index-modifying operation is executing at any point of time. So in short, you can have multiple search operations and not more than one index update (add and/or delete) operation in progress at any time and that should not corrupt the index.
Thanks, Aalap. --- Maik Schreiber <[EMAIL PROTECTED]> wrote: > > My problem is that the index update procedure and > the searches could run > > simultaneously, and, if they do, they corrupt the > index file. > > Is there a way to let Lucene handle this > concurrency automatically (like > > stop the searches till the update is finished)? > > Lucene does not handle this by itself but relies on > outside synchronization. > You might want to have a look at LuceneIndexAccessor > (please see > http://issues.apache.org/bugzilla/show_bug.cgi?id=34995) > > -- > Maik Schreiber * http://www.blizzy.de > > GPG public key: > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x1F11D713 > Key fingerprint: CF19 AFCE 6E3D 5443 9599 18B5 5640 > 1F11 D713 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > __________________________________ Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
