DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12588>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12588 Delete failed after new Term is indexed ------- Additional Comments From [EMAIL PROTECTED] 2002-09-12 19:31 ------- Second thought. The option (a) is not valid either. What happen if: reader1.open() reader2.open() reader1.delete(documentA) reader2.delete(documentB) Document A will be restored by the second, since reader2 does not know document A has been deleted by reader1. Maybe a better solution is to create an IndexDeleter that is a subclass of IndexReader. It should obtain the write lock in the constructor as IndexWriter does, and write the delete file and release the write lock in the close method as IndexReader does. The makeLock(String name) should also take a maximum wait time argument. It should try to obtain the lock during that period of time, and return false only after the time is expired. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
