You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by "Nicolas Brel (JIRA)" <ji...@apache.org> on 2006/07/11 22:51:30 UTC

[jira] Created: (LUCENENET-10) Supporting deleteDocuments in IndexWriter

Supporting deleteDocuments in IndexWriter
-----------------------------------------

         Key: LUCENENET-10
         URL: http://issues.apache.org/jira/browse/LUCENENET-10
     Project: Lucene.Net
        Type: New Feature

    Reporter: Nicolas Brel


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_string=indexwriter%20delete;#23049 



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


unsubscribe

Posted by Sergiy Savchenko <ma...@gmail.com>.

-----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.



unsubscribe

Posted by Adam Hurwitz - BIA <ah...@biaprotect.com>.
 

-----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.



[jira] Updated: (LUCENENET-10) Supporting deleteDocuments in IndexWriter

Posted by "Nicolas Brel (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/LUCENENET-10?page=all ]

Nicolas Brel updated LUCENENET-10:
----------------------------------

    Attachment: IndexWriter.patch

Patch for lucene.Net  1.9 RC1

> Supporting deleteDocuments in IndexWriter
> -----------------------------------------
>
>          Key: LUCENENET-10
>          URL: http://issues.apache.org/jira/browse/LUCENENET-10
>      Project: Lucene.Net
>         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_string=indexwriter%20delete;#23049 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (LUCENENET-10) Supporting deleteDocuments in IndexWriter

Posted by "Digy (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENENET-10?page=com.atlassian.jira.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_string=indexwriter%20delete;#23049 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (LUCENENET-10) Supporting deleteDocuments in IndexWriter

Posted by "George Aroush (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENENET-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

George Aroush closed LUCENENET-10.
----------------------------------

    Resolution: Fixed

I agree with Digy.  I'm closing this as "Fixed" but it really should be labeled as "Fixed-indirectly".

-- George

> 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_string=indexwriter%20delete;#23049 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.