[ https://issues.apache.org/jira/browse/HADOOP-9371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666838#comment-13666838 ]
Konstantin Shvachko commented on HADOOP-9371: --------------------------------------------- Steve, you might want to link the document from github to the jira. Add Link has an option to add a web link. Not requiring atomicity for mkdirs() and recursive deletes makes sense to me. For renames I think we should also restrict atomicity to one special case, when file or directory name changes, that is file is not moving from one directory to another. I call it in-place rename, which with inode numbers in place is a trivial operation. Atomic moves are hard if you build a distributed namespace service (like Giraffa). Moving a file between directories that are located on different nodes requires distributed coordination, which can be complex. > Define Semantics of FileSystem and FileContext more rigorously > -------------------------------------------------------------- > > Key: HADOOP-9371 > URL: https://issues.apache.org/jira/browse/HADOOP-9371 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs > Affects Versions: 1.2.0, 3.0.0 > Reporter: Steve Loughran > Assignee: Steve Loughran > Attachments: HADOOP-9361.2.patch, HADOOP-9361.patch, > HadoopFilesystemContract.pdf > > Original Estimate: 48h > Remaining Estimate: 48h > > The semantics of {{FileSystem}} and {{FileContext}} are not completely > defined in terms of > # core expectations of a filesystem > # consistency requirements. > # concurrency requirements. > # minimum scale limits > Furthermore, methods are not defined strictly enough in terms of their > outcomes and failure modes. > The requirements and method semantics should be defined more strictly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira