[ https://issues.apache.org/jira/browse/HADOOP-13134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267968#comment-16267968 ]
Zichen Sun commented on HADOOP-13134: ------------------------------------- We had a similar issue reported a few times when doing delete directories, and the workaround was to set fs.azure.flatlist.enable to true, introduced by https://issues.apache.org/jira/browse/HADOOP-13403, which skips the following if (!enableFlatListing) { // Currently at a depth of one, decrement the listing depth for // sub-directories. buildUpList(directory, fileMetadata, maxListingCount,maxListingDepth - 1);} > 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: Dushyanth > > 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 (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org