[
https://issues.apache.org/jira/browse/HADOOP-13134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16109792#comment-16109792
]
Steve Loughran commented on HADOOP-13134:
-----------------------------------------
there's a set of things which object stores often let you do, and which the
blobstore clients often unintentionally let you continue to do, which break our
fundamental expectations of an FS
* create files under files
* create directories under files
* rename things under themselves via copy (unless you try hard to detect and
stop this)
+ others
most of these surface the stricter the tests we do for FS compliance. They tend
not to surface in the wild as much, because people writing code assume that the
far end is a filesystem, so their code conforms to the set of shared
assumptions.
Here's a case of it. Given it's actually happening in the hadoop file output
committer, it may surface in production, so I think mertis fixing. The other
ones, the ones which only show up if we discover a bug in our own mental model
of filesystems and write tests for themn, those I worry less about.
> 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: [email protected]
For additional commands, e-mail: [email protected]
