[
https://issues.apache.org/jira/browse/HADOOP-13134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346339#comment-16346339
]
Rohan Garg commented on HADOOP-13134:
-------------------------------------
Thanks for the analysis and the advice. Yes, I will start a spark JIRA for
this. Yes, I will turn on caching to ensure correctness and performance.
I agree that finalize in azure FS was trying to help by closing the fs. It
should be the responsibility of the client to manage or preserve the FS object
if certain behaviors are to be expected from it (esp. the ones which rely on
GC, close etc.).
> WASB's file delete still throwing Blob not found exception
> ----------------------------------------------------------
>
> Key: HADOOP-13134
> URL: https://issues.apache.org/jira/browse/HADOOP-13134
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 2.7.1
> Reporter: Lin Chan
> Assignee: Thomas Marquardt
> Priority: Major
>
> WASB is still throwing blob not found exception as shown in the following
> stack. Need to catch that and convert to Boolean return code in WASB delete.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
