> > However, after optimizing, suddenly those new documents > > appear. Its almost as if the new segments are not being read > > by the IndexReader. > > You need to close IndexWriter before open IndexReader. Or reopen > IndexReader. > > See TestIndexReader.java:: private void deleteReaderWriterConflict(boolean > optimize) throws IOException > for more info.
I don't think that is the problem since I'm starting a complete new IndexReader after an indexing process has completed in a new jvm. But reading the TestIndexReader I found this: // REQUEST OPTIMIZATION // This causes a new segment to become current for all subsequent // searchers. Because of this, deletions made via a previously open // reader, which would be applied to that reader's segment, are lost // for subsequent searchers/readers Does this mean I have optimize for my new segments to be recognized? Roy. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
