[
https://issues.apache.org/jira/browse/LUCENE-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016375#comment-13016375
]
Christian Danninger commented on LUCENE-3015:
---------------------------------------------
Sorry about that, you are right.
I'll close the ticket.
> UDIDIndexWriter keeps write lock on corrupt index
> -------------------------------------------------
>
> Key: LUCENE-3015
> URL: https://issues.apache.org/jira/browse/LUCENE-3015
> 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
