lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Updated: (LUCENE-2513) IndexReader overwrites future commits when you open it on a past commit
Date Thu, 24 Jun 2010 14:37:49 GMT


Michael McCandless updated LUCENE-2513:

    Attachment: LUCENE-2513.patch

> IndexReader overwrites future commits when you open it on a past commit
> -----------------------------------------------------------------------
>                 Key: LUCENE-2513
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 3.1, 4.0
>         Attachments: LUCENE-2513.patch
> Hit this on trying to build up a test index for perf testing...
> IndexReader (and Writer) accept an IndexCommit on open.
> This is quite powerful, because, if you use a deletion policy that keeps multiple commits
around, you can open a not-current commit, make some changes, write a new commit, all without
altering the "future" commits.
> I use this to first build up a big wikipedia index, including one commit w/ multiple
segments, then another commit after optimize(), and then I open an writable IR to perform
deletions off of both those commits.  This gives me a single test index that has all four
combinations (single vs multi segment; deletions vs no deletions).
> But IndexReader has a bug whereby it overwrites the segments_N file.  (IndexWriter works

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