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

Hudson commented on HADOOP-16785:
---------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #17830 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/17830/])
HADOOP-16785. Improve wasb and abfs resilience on double close() calls. 
(stevel: rev 17aa8f6764262767b42717cf190a53e2c1795507)
* (edit) 
hadoop-tools/hadoop-azure/src/test/java/org/apache/hadoop/fs/azure/AbstractWasbTestBase.java
* (edit) 
hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azure/NativeAzureFileSystem.java
* (edit) 
hadoop-tools/hadoop-azure/src/test/java/org/apache/hadoop/fs/azure/ITestFileSystemOperationExceptionHandling.java
* (edit) 
hadoop-tools/hadoop-azure/src/test/java/org/apache/hadoop/fs/azurebfs/ITestAzureBlobFileSystemCreate.java
* (edit) 
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/test/LambdaTestUtils.java
* (edit) 
hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azurebfs/services/AbfsOutputStream.java


> 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
>
> # 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]

Reply via email to