[jira] Updated: (LUCENE-808) bufferDeleteTerm in IndexWriter might flush prematurely

2007-06-05 Thread Doron Cohen (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Doron Cohen updated LUCENE-808:
---

Priority: Minor  (was: Major)

 bufferDeleteTerm in IndexWriter might flush prematurely
 ---

 Key: LUCENE-808
 URL: https://issues.apache.org/jira/browse/LUCENE-808
 Project: Lucene - Java
  Issue Type: Bug
  Components: Index
Affects Versions: 2.1
Reporter: Doron Cohen
Assignee: Doron Cohen
Priority: Minor
 Attachments: successive_bufferDeleteTerm.patch


 Successive calls to remove-by-the-same-term would increment 
 numBufferedDeleteTerms
 although all but the first are no op if no docs were added in between. Hence 
 deletes would
 be flushed too soon.
 It is a minor problem, should be rare, but it seems cleaner to fix this. 
 Attached patch also fixes TestIndexWriterDelete.testNonRAMDelete() which 
 somehow
 relied on this behavior.  All tests pass.

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


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (LUCENE-808) bufferDeleteTerm in IndexWriter might flush prematurely

2007-02-21 Thread Doron Cohen (JIRA)

 [ 
https://issues.apache.org/jira/browse/LUCENE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Doron Cohen updated LUCENE-808:
---

Attachment: successive_bufferDeleteTerm.patch

 bufferDeleteTerm in IndexWriter might flush prematurely
 ---

 Key: LUCENE-808
 URL: https://issues.apache.org/jira/browse/LUCENE-808
 Project: Lucene - Java
  Issue Type: Bug
  Components: Index
Affects Versions: 2.1
Reporter: Doron Cohen
 Attachments: successive_bufferDeleteTerm.patch


 Successive calls to remove-by-the-same-term would increment 
 numBufferedDeleteTerms
 although all but the first are no op if no docs were added in between. Hence 
 deletes would
 be flushed too soon.
 It is a minor problem, should be rare, but it seems cleaner to fix this. 
 Attached patch also fixes TestIndexWriterDelete.testNonRAMDelete() which 
 somehow
 relied on this behavior.  All tests pass.

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


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]