If you are performing additions and deletions then you should serially create an IndexReader to do deletions, close it, then create an IndexWriter to do additions, close it, and so on. Note that typically one will use a different IndexReader for deletions than is used for searching, so that searches may continue while adding documents.
Doug > -----Original Message----- > From: Avi Drissman [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, November 27, 2001 1:47 PM > To: Lucene Users List > Subject: IndexReader and IndexWriter on the same index > > > In the FAQ in Searching question 41, it says about index > modification: "The problems are only when you add documents or > optimize an index, and then search with an IndexReader that was > constructed before those changes to the index were made." > > I'm in a situation where before I add any document I need to remove > any old versions of it from the index. I'd like to keep both an > IndexReader and IndexWriter around for efficiency's sake, but I'm > concerned about them interacting properly. Does the delete(Term) > member function count as a "search" in the above statement? Can I > delete with an IndexReader, add with an IndexWriter, delete with that > IndexReader, add with that IndexWriter, etc. without concern, or must > I recreate one (or both) of them each time? > > Thanks. > > Avi > -- > Avi Drissman > [EMAIL PROTECTED] > Bit bashing since 1977 > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
