You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2010/07/13 18:50:50 UTC

[jira] Resolved: (LUCENE-2536) Rollback doesn't preserve integrity of original index

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

Michael McCandless resolved LUCENE-2536.
----------------------------------------

    Fix Version/s: 2.4.2
                   2.9.4
                   3.0.3
                   3.1
                   4.0
       Resolution: Fixed

Thanks Mark -- what a doozie!

> 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
>             Fix For: 2.4.2, 2.9.4, 3.0.3, 3.1, 4.0
>
>         Attachments: LUCENE-2536.patch, LUCENE-2536.patch, 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