lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-2536) Rollback doesn't preserve integrity of original index
Date Tue, 13 Jul 2010 14:35:50 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887775#action_12887775
] 

Michael McCandless commented on LUCENE-2536:
--------------------------------------------

Duh -- in DocumentsWriter.abort, right after deletesInRAM.clear() we must add deletesFlush.clear().
 So, indeed, any deletions pending (either due to .updateDoc or .deleteDocs) when segments
were flushed, fail to be cleared and are then applied on close.

How awful!

> Rollback doesn't preserve integrity of original index
> -----------------------------------------------------
>
>                 Key: LUCENE-2536
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2536
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 3.0.2
>         Environment: Windows XP pro
>            Reporter: Mark Harwood
>            Assignee: Michael McCandless
>         Attachments: TestRollback.java, TestRollback.java
>
>
> After several "updateDocuments" calls a rollback call does not return the index to the
prior state.
> This seems to occur if the number of updates exceeds the RAM buffer size i.e. when some
flushing of updates occurs.
> Test fails in Lucene 2.4, 2.9, 3.0.1 and 3.0.2
> JUnit to follow.

-- 
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message