[
https://issues.apache.org/jira/browse/LUCENE-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776982#action_12776982
]
Michael McCandless commented on LUCENE-2053:
--------------------------------------------
How about ThreadInterruptedException? Maybe under oal.util?
I wouldn't restrict the name/scope to indexing. Sure, maybe today you can't
Thread.interrupt a Lucene search, but maybe in the future we'll allow that and
then this same exception should be thrown.
I think it's cleaner to extend RuntimeException. Right now (2.9) you get a
RuntimeException, so extending IOException instead is more of a back compat
break.
I just wish InterruptedException had been non-checked from the get-go...
> When thread is interrupted we should throw a clear exception
> ------------------------------------------------------------
>
> Key: LUCENE-2053
> URL: https://issues.apache.org/jira/browse/LUCENE-2053
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Priority: Minor
> Fix For: 3.0
>
>
> This is the 3.0 followon from LUCENE-1573. We should throw a dedicated
> exception, not just RuntimeException.
> Recent discussion from java-dev "Thread.interrupt()" subject:
> http://www.lucidimagination.com/search/document/8423f9f0b085034e/thread_interrupt
--
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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
