I agree -- I'll reopen & add 2.4.1 fix version. Can you back port the fix?

Mike

Mark Miller wrote:

The broken getPayloads from nearspanordered should prob make this list. It makes the spans getpayloads stuff pretty much unusable as is (unless you happen to only use nearspanordered with fields that don't have repeating terms or...).

Michael McCandless (JIRA) wrote:
[ https://issues.apache.org/jira/browse/LUCENE-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652784 #action_12652784 ]
Michael McCandless commented on LUCENE-1474:
--------------------------------------------

There are no concrete plans / timing for a 2.4.1 release, but I think it's likely it'll eventually happen if we accumulate enough issues to backport.

I'll reopen this & add 2.4.1 fix version so we don't lose track of it...


Incorrect SegmentInfo.delCount when IndexReader.flush() is used
---------------------------------------------------------------

               Key: LUCENE-1474
URL: https://issues.apache.org/jira/browse/ LUCENE-1474
           Project: Lucene - Java
        Issue Type: Bug
        Components: Index
  Affects Versions: 2.4
          Reporter: Marcel Reutegger
          Assignee: Michael McCandless
           Fix For: 2.4.1, 2.9

       Attachments: IndexReaderTest.java


When deleted documents are flushed using IndexReader.flush() the delCount in SegmentInfo is updated based on the current value and SegmentReader.pendingDeleteCount (introduced by LUCENE-1267). It seems that pendingDeleteCount is not reset after the commit, which means after a second flush() or close() of an index reader the delCount in SegmentInfo is incorrect. A subsequent IndexReader.open() call will fail with an error when assertions are enabled. E.g.: java.lang.AssertionError: delete count mismatch: info=3 vs BitVector=2 at org .apache .lucene.index.SegmentReader.loadDeletedDocs(SegmentReader.java:405)
[...]





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



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

Reply via email to