Return-Path: Delivered-To: apmail-lucene-java-dev-archive@www.apache.org Received: (qmail 85847 invoked from network); 16 Feb 2007 19:32:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Feb 2007 19:32:31 -0000 Received: (qmail 83095 invoked by uid 500); 16 Feb 2007 19:32:34 -0000 Delivered-To: apmail-lucene-java-dev-archive@lucene.apache.org Received: (qmail 83059 invoked by uid 500); 16 Feb 2007 19:32:34 -0000 Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@lucene.apache.org Delivered-To: mailing list java-dev@lucene.apache.org Received: (qmail 83043 invoked by uid 99); 16 Feb 2007 19:32:34 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Feb 2007 11:32:34 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Feb 2007 11:32:25 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A5D8B7141E1 for ; Fri, 16 Feb 2007 11:32:05 -0800 (PST) Message-ID: <1929172.1171654325677.JavaMail.jira@brutus> Date: Fri, 16 Feb 2007 11:32:05 -0800 (PST) From: "Hoss Man (JIRA)" To: java-dev@lucene.apache.org Subject: [jira] Commented: (LUCENE-793) Javadocs should explain possible causes for IOExceptions In-Reply-To: <13949234.1170411545499.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/LUCENE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473798 ] Hoss Man commented on LUCENE-793: --------------------------------- > * Changed some places where we were throwing IllegalStateException > to throw CorruptIndexException instead shouldn't this be considered a major API change? people previously catching IllegalStateException to try and deal with this differently from an IOException will now be caching the "CorruptIndexException" as a subclass of IOException. I haven't read the details of the patch, but perhaps CorruptIndexException should be a subclass of IllegalStateException to be backwards compatible? > 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: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org