[
https://issues.apache.org/jira/browse/HADOOP-16785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011497#comment-17011497
]
Thomas Marqardt commented on HADOOP-16785:
------------------------------------------
I’m not setup to build/test at the moment, so could you use two streams writing
to the same file and verify whether or not there is actually another issue? I
hope FilterOutputStream.close calls AbfsOutputStream.close and there is not an
issue.
> Improve wasb and abfs resilience on double close() calls
> --------------------------------------------------------
>
> Key: HADOOP-16785
> URL: https://issues.apache.org/jira/browse/HADOOP-16785
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.2.1
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Fix For: 3.2.2
>
>
> # if you call write() after the NativeAzureFsOutputStream is closed it throws
> an NPE ... which isn't always caught by closeQuietly code. It needs to raise
> an IOE
> # abfs close ops can trigger failures in try-with-resources use
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
