[ https://issues.apache.org/jira/browse/LUCENE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473847 ]
Hoss Man commented on LUCENE-793: --------------------------------- > Since these really are cases of severe index corruption I thought it > best to throw CorruptIndexException instead? no disagreement, i'm just not clear on why "CorruptIndexException" (which is a completley new Exception type created by your patch correct?) should be a subclass of IOException instead of IllegalStateException. > Javadocs should explain possible causes for IOExceptions > -------------------------------------------------------- > > Key: LUCENE-793 > URL: https://issues.apache.org/jira/browse/LUCENE-793 > Project: Lucene - Java > Issue Type: Bug > Components: Javadocs > Reporter: Michael McCandless > Assigned To: Michael McCandless > Priority: Minor > Attachments: LUCENE-793.patch > > > Most methods in Lucene reserve the right to throw an IOException. This can > occur for nearly all methods from low level problems like wrong permissions, > transient IO errors, bad hard drive or corrupted file system, corrupted > index, etc, but for some methods there are also more interesting causes that > we should try to document. > Spinoff of this thread: > http://www.gossamer-threads.com/lists/lucene/java-user/44929 -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]