Luke can't open (read only) on an index that is being written to?

GoogleCodeExporter commented 8 years ago

I have a background task writing to an index and periodically committing. I 
wanted to use Luke to open the index to examine the index contents and selected 
the "open read only" option.
However I get an error message "Index is locked and Read-Only. Open for 
read-write and 'Force unlock'". Forcing an unlock seems unnecessary (and 
inadvisable!) given that I can open the same index as follows without a problem:
    public static void main(String[] args) throws Exception
    {
        FSDirectory dir = FSDirectory.open(new File("c:/indexes/myIndex"));
        IndexReader r = IndexReader.open(dir, true);
        System.out.println(r.numDocs());
        r.close();
    }

Is this a Luke bug or a (new?) limitation of how the app is put together?

Windows 64bit, Luke v3.4.0(2011-10-03).

Cheers,
Mark

Original issue reported on code.google.com by MarkHarw...@gmail.com on 11 Oct 2011 at 10:44

GoogleCodeExporter commented 8 years ago

I am seeing the same error with v3.3 and 3.4 on linux 64bit.

Original comment by mmilazz...@gmail.com on 14 Dec 2011 at 7:38

GoogleCodeExporter commented 8 years ago

Confirmed - this bug is fixed in the upcoming 3.5.0. Thanks for reporting.

Original comment by sig...@gmail.com on 28 Dec 2011 at 2:21

Changed state: Fixed

pakoju / luke

Luke can't open (read only) on an index that is being written to? #49