You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2014/09/01 13:18:21 UTC
[jira] [Created] (HADOOP-11042) CryptoInputStream throwing wrong
exception class on erros
Steve Loughran created HADOOP-11042:
---------------------------------------
Summary: CryptoInputStream throwing wrong exception class on erros
Key: HADOOP-11042
URL: https://issues.apache.org/jira/browse/HADOOP-11042
Project: Hadoop Common
Issue Type: Bug
Components: fs
Affects Versions: 3.0.0
Reporter: Steve Loughran
Having had a quick look at the {{CryptoInputStream}} class, it's not in sync with all the other filesystem's exception logic, as specified in {{src/site/markdown/filesystem/fsdatainputstream.md}}
Operations MUST throw an {{IOException}} on out of bounds reads, ideally {{EOFException}} :
# {{read(byte[] b, int off, int len)}}
# {{seek(long pos) }}
# {{seekToNewSource}}
The tests you want to extend to verify expected behaviour are in {{AbstractContractOpenTest}} and {{AbstractContractSeekTest}}
also, the {{HasEnhancedByteBufferAccess}} implementations may want to think about using {{checkStream()}} before acting on a potentially closed stream.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)