In my experience, reopen will find all changes on an index, whether it was modified by the same process or not. If you're replicating over a network, you might need some barrier / lock around the reopen call to make sure the replicated index is complete. Obviously with something as fickle as a network, you may need some extra protection around this. It has worked best for me to replicate using IndexWriter wrapping some transport protocol.
--dho On Oct 16, 2011 10:33 PM, "Denis Bazhenov" <dot...@gmail.com> wrote: > We have situation when lucene index is replicated over network. And on that > machine reader reopen doesn't make new documents visible to a search. > > As far as I know IndexReader.reopen() call does work only if changes are > applied using the linked IndexWriter. My question is: how can I implement > efficient index reopen (only new segments should be read) when index is > changed externally? > --- > Denis Bazhenov <dot...@gmail.com> > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >
