hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14346) CryptoOutputStream throws IOException on flush() if stream is closed
Date Thu, 27 Apr 2017 11:24:04 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986388#comment-15986388

Steve Loughran commented on HADOOP-14346:

Committed to branch-2.8+, thanks. 

> 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
>            Assignee: Pierre Lacave
>             Fix For: 2.8.1
>         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

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

View raw message