lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Resolved: (LUCENE-1449) IndexDeletionPolicy.delete behaves incorrectly when deleting latest generation
Date Tue, 11 Nov 2008 22:43:44 GMT


Michael McCandless resolved LUCENE-1449.

       Resolution: Fixed
    Fix Version/s: 2.9

Committed revision 713206.

Thanks Mark!

> IndexDeletionPolicy.delete behaves incorrectly when deleting latest generation 
> -------------------------------------------------------------------------------
>                 Key: LUCENE-1449
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.9
>            Reporter: Mark Harwood
>            Assignee: Michael McCandless
>            Priority: Minor
>             Fix For: 2.9
>         Attachments: LUCENE-1449.patch, LUCENE-1449.patch,,
> I have been looking to provide the ability to rollback committed transactions and encountered
some issues.
> I appreciate IndexDeletionPolicy's main motivation is to handle cleaning away OLD commit
points but it does not explicitly state that it can or cannot be used to clean NEW commit
> If this is not supported then the documentation should ideally state this. If the intention
is to support this behaviour then read on .......
> There seem to be 2 issues so far:
> 1) The first attempt to call IndexCommit.delete on the latest commit point fails to remove
any contents. The subsequent call succeeds however
> 2) Deleting the latest commit point fails to update the segments.gen file to point to
segments_N-1. New IndexReaders that are opened are then misdirected to open segments_N which
has been deleted
> Junit test 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:
For additional commands, e-mail:

View raw message