[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538011#comment-13538011
]
Mark Miller commented on LUCENE-4246:
-------------------------------------
What I'm really dying for is just a close that is sure to close. Whatever
problems it encounters, whatever goes wrong - sure, I'd like to know about it -
but please still close and release the writer lock. I know my index will still
be good up till the last commit and I can open a new IndexWriter. I really need
this for some tests - mainly because jetty and/or the test framework can
interrupt threads - this can cause interruption exceptions and channel
interruption exceptions that kill the close. For a std interruption exception I
seem to be able to retry close and succeed - but not a channel interruption
exception.
> Fix IndexWriter.close() to not commit or wait for pending merges
> ----------------------------------------------------------------
>
> Key: LUCENE-4246
> URL: https://issues.apache.org/jira/browse/LUCENE-4246
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Assignee: Robert Muir
> Fix For: 4.1
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
