You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2013/06/08 00:20:20 UTC

[jira] [Commented] (HADOOP-9371) Define Semantics of FileSystem and FileContext more rigorously

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

Suresh Srinivas commented on HADOOP-9371:
-----------------------------------------

Steve,

What you are trying do in this jira? Because some of the comments in this jira suggests changing the semantics.

Is your intent to document the semantics rigorously and add tests to ensure any other file system implementation can be tested (I do not know how you can test atomicity easily) and certified based on these tests? or Are you also planning to change the semantics?

As regards to deciding the semantics, where the documentation is either sparse or not clear, the semantics as implemented by HDFS is the gold standard. Because that is what majority of applications are dependent upon. I would discourage others from second guessing what applications need, because we do not know all the applications that are out there.
                
> 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