lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Commented: (LUCENE-793) Javadocs should explain possible causes for IOExceptions
Date Fri, 16 Feb 2007 20:08:05 GMT


Michael McCandless commented on LUCENE-793:

You're right, technically this is an API change.

The only cases I changed were the ones stemming from LUCENE-140: the
original "docs out of order" corruption plus 2 other consisteny checks
I had added as part of the fix for LUCENE-140.

(There are other places where Lucene throws a IllegalStateException
that I did not change.)

I think it's extremely unlikely users are relying on the
IllegalStateException specifically (ie catching it explicitly and
doing something about it)?

EG these particular cases were never listed in the "throws"
(IllegalStateException is unchecked).  And if you hit this exception
your index truly is corrupt.

Since these really are cases of severe index corruption I thought it
best to throw CorruptIndexException instead?

> Javadocs should explain possible causes for IOExceptions
> --------------------------------------------------------
>                 Key: LUCENE-793
>                 URL:
>             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:

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:
For additional commands, e-mail:

View raw message