lucene-dev mailing list archives

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

                 Key: LUCENE-2513
                 URL: https://issues.apache.org/jira/browse/LUCENE-2513
             Project: Lucene - Java
          Issue Type: Bug
          Components: Index
            Reporter: Michael McCandless
            Assignee: Michael McCandless
             Fix For: 3.1, 4.0


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 correctly).

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