lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3015) UDIDIndexWriter keeps write lock on corrupt index
Date Wed, 06 Apr 2011 13:47:05 GMT


Uwe Schindler commented on LUCENE-3015:

What are you talking about? Lucene has no class "UDIDIndexWriter", so maybe thats an external

If this is the case, I will close the issue.

> UDIDIndexWriter keeps write lock on corrupt index
> -------------------------------------------------
>                 Key: LUCENE-3015
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.9.3
>         Environment: Lucene 2.9.3
>            Reporter: Christian Danninger
> Try to open an index writer with 
> new UDIDIndexWriter(directory, new FakeAnalyzer(), false);
> keeps a write.lock.
> Creating the IndexWriter will succeed, but a subsequent call to UDIDIndexWriter.getCounter()
in the constructor failes.
> There are no possibilites to remove write.lock per an API call.
> The index writer is used to optimize the index, the index itself will be created by an
different index. So after some time the index will be valid again, but the write lock still
exists. So the process has to ended first an afterward the write lock could be removed.

This message is automatically generated by JIRA.
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message