[
https://issues.apache.org/jira/browse/LUCENE-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1411.
----------------------------------------
Resolution: Fixed
> Enable IndexWriter to open an arbitrary commit point
> ----------------------------------------------------
>
> Key: LUCENE-1411
> URL: https://issues.apache.org/jira/browse/LUCENE-1411
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Affects Versions: 2.4
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Priority: Minor
> Fix For: 2.9
>
> Attachments: LUCENE-1411.patch
>
>
> With a 2-phase commit involving multiple resources, each resource
> first does its prepareCommit and then if all are successful they each
> commit. If an exception or timeout/power loss is hit in any of the
> resources during prepareCommit or commit, all of the resources must
> then rollback.
> But, because IndexWriter always opens the most recent commit, getting
> Lucene to rollback after commit() has been called is not easy, unless
> you make Lucene the last resource to commit. A simple workaround is
> to simply remove the segments_N files of the newer commits but that's
> sort of a hassle.
> To fix this, we just need to add a ctor to IndexWriter that takes an
> IndexCommit. We recently added this for IndexReader (LUCENE-1311) as
> well. This ctor is definitely an "expert" method, and only makes
> sense if you have a custom DeletionPolicy that preserves more than
> just the most recent commit.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
