lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-8525) throw more specific exception on data corruption
Date Tue, 08 Jan 2019 11:21:00 GMT


Robert Muir commented on LUCENE-8525:

Sorry, this isn't the job of the library to classify exceptions into these buckets you seem
to want (Such as recoverable or not), we simply do not know this. and the EOF case is a perfect
example of every other case, where its really ambiguous what the cause is.

We can pass along the problems as exceptions and that is really it: no more. Historically
that has been difficult enough: it is enough to ensure the IOException makes it through unswallowed.
the exception handling is already too complex, it should not be made even more so for artificial

plain ioexception is perfectly fine. callers really shouldnt be handling anything. if you
want to try to do this magical determination when an ioexception strikes, I think you are
going to have to figure out what heuristic you want, and write code yourself to do it (e.g.
invoke checksum verification code or whatever you decide).

> throw more specific exception on data corruption
> ------------------------------------------------
>                 Key: LUCENE-8525
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Vladimir Dolzhenko
>            Priority: Major
> DataInput throws generic IOException if data looks odd
> [DataInput:141|]
> there are other examples like [BufferedIndexInput:219|],
and maybe [DocIdsWriter:81|]
> That leads to some difficulties - see [elasticsearch #34322|]
> It would be better if it throws more specific exception.
> As a consequence [SegmentInfos.readCommit|]
violates its own contract
> {code:java}
> /**
>    * @throws CorruptIndexException if the index is corrupt
>    * @throws IOException if there is a low-level IO error
>    */
> {code}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message