lucene-dev mailing list archives

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

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

Shai Erera updated LUCENE-2536:
-------------------------------

    Attachment: TestRollback.java

It did not fail for me on 3.1, however did fail on 3.0.1.

I'm attaching a version of this test, which creates far less docs (5, instead of 10,000) and
uses a RAMDirectory). The test still fails, which is expected. I assume if we want to make
that an official unit test, the test case which passes should go away? (or not)

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