Mailing List Archive

DO NOT REPLY [Bug 12588] New: - Delete failed after new Term is indexed
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

Summary: Delete failed after new Term is indexed
Product: Lucene
Version: 1.2
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Index
AssignedTo: lucene-dev@jakarta.apache.org
ReportedBy: tlai@leversoft.com


Deleting documents from a reader has no permanent effect if the reader is
opened before a writer is used to index new documents. This is similar to bug
6140 (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6140) reported before,
although I don’t think it is a multi-thread issue. The following pseudo-code
caused the problem:

reader.open()

writer.open()
writer.add(documentB)
writer.close()

reader.delete(documentA)
reader.close()

searcher.open()
searcher.search("term_common_to_docA_and_docB")
// This returns both docA and docB

Please see my attached test class, which is single threaded. I believe the
option (a) and (b) suggested in BUG 6140 are valid, but not necessary (C).

--
To unsubscribe, e-mail: <mailto:lucene-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:lucene-dev-help@jakarta.apache.org>