[ https://issues.apache.org/jira/browse/HADOOP-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985535#comment-15985535 ]
Pierre Lacave commented on HADOOP-14346: ---------------------------------------- so we'll fix the druid case in druid (cleaning up those late flush), feel free to close this issue if you think the current CryptoOutputStream flush behaviour is fine. Thanks > 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, > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org