-----Original Message----- From: Adam Hurwitz - BIA [mailto:ahurwitz@biaprotect.com] Sent: Thursday, August 23, 2007 11:45 AM To: lucene-net-dev@incubator.apache.org Subject: unsubscribe -----Original Message----- From: Digy (JIRA) [mailto:jira@apache.org] Sent: Thursday, August 23, 2007 11:11 AM To: lucene-net-dev@incubator.apache.org Subject: [jira] Commented: (LUCENENET-10) Supporting deleteDocuments in IndexWriter [ https://issues.apache.org/jira/browse/LUCENENET-10?page=com.atlassian.ji ra.plugin.system.issuetabpanels:comment-tabpanel#action_12522169 ] Digy commented on LUCENENET-10: ------------------------------- With Lucene.Net v2.1, IndexWriter has DeleteDocuments method > Supporting deleteDocuments in IndexWriter > ----------------------------------------- > > Key: LUCENENET-10 > URL: https://issues.apache.org/jira/browse/LUCENENET-10 > Project: Lucene.Net > Issue Type: New Feature > Reporter: Nicolas Brel > Attachments: IndexWriter.patch > > > Excerpt from the bug submited by Ning Li for Java Lucene: > Today, applications have to open/close an IndexWriter and open/close > an IndexReader directly or indirectly (via IndexModifier) in order to > handle a mix of inserts and deletes. This performs well when inserts > and deletes come in fairly large batches. However, the performance can > degrade dramatically when inserts and deletes are interleaved in small batches. > This is because the ramDirectory is flushed to disk whenever an > IndexWriter is closed, causing a lot of small segments to be created > on disk, which eventually need to be merged. > We would like to propose a small API change to eliminate this problem. > We are aware that this kind change has come up in discusions before. > See > http://www.gossamer-threads.com/lists/lucene/java-dev/23049?search_str > ing=indexwriter%20delete;#23049 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.