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 "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/04/23 21:13:04 UTC
[jira] [Commented] (HADOOP-14346) CryptoOutputStream throws
IOException if stream is closed which is not the standard OutputStream
behaviour
[ https://issues.apache.org/jira/browse/HADOOP-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980529#comment-15980529 ]
Hadoop QA commented on HADOOP-14346:
------------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 7s{color} | {color:red} HADOOP-14346 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-14346 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12864651/CryptoOutputStream.flush-no-throw-on-closed.patch |
| Console output | https://builds.apache.org/job/PreCommit-HADOOP-Build/12166/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> CryptoOutputStream throws IOException if stream is closed which is not the standard OutputStream behaviour
> -----------------------------------------------------------------------------------------------------------
>
> 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
>
>
> 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