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 2017/04/27 11:20:04 UTC

[jira] [Updated] (HADOOP-14346) CryptoOutputStream throws IOException on flush() if stream is closed

     [ https://issues.apache.org/jira/browse/HADOOP-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran updated HADOOP-14346:
------------------------------------
    Summary: CryptoOutputStream throws IOException on flush() if stream is closed  (was: CryptoOutputStream throws IOException if stream is closed which is not the standard OutputStream behaviour )

> CryptoOutputStream throws IOException on flush() if stream is closed
> --------------------------------------------------------------------
>
>                 Key: HADOOP-14346
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14346
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 2.7.3
>            Reporter: Pierre Lacave
>         Attachments: CryptoOutputStream.flush-no-throw-on-closed.patch, HADOOP-14346-1.patch
>
>
> With Druid and Hadoop 2.7.3 I see that calls to flush() on a closed CryptoOutputStream throws IOException.
> Although flushing closed stream is dodgy, the culprit is actually CryptoOutputStream, according to the java documentation it look actually authorised.
> The OutputStream java doc (http://docs.oracle.com/javase/8/docs/api/java/io/OutputStream.html#flush()) shows that flush should behave like close(), which allows being called on a closed stream without exception (as opposed to write() and others which clearly says should throw an exception)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org