You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2007/02/21 21:03:05 UTC
[jira] Resolved: (LUCENE-793) Javadocs should explain possible
causes for IOExceptions
[ https://issues.apache.org/jira/browse/LUCENE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael McCandless resolved LUCENE-793.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.2
OK, I just committed this. I stuck with the original approach (basing CorruptIndexException on IOException).
> 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
> Fix For: 2.2
>
> 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org