hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] [Moved] (HADOOP-11579) Add definition of truncate preconditions/postconditions to filesystem specification
Date Wed, 11 Feb 2015 00:01:13 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-11579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Konstantin Shvachko moved HDFS-7665 to HADOOP-11579:
----------------------------------------------------

          Component/s:     (was: documentation)
                       documentation
        Fix Version/s:     (was: 3.0.0)
    Affects Version/s:     (was: 3.0.0)
                       2.7.0
                  Key: HADOOP-11579  (was: HDFS-7665)
              Project: Hadoop Common  (was: Hadoop HDFS)

> Add definition of truncate preconditions/postconditions to filesystem specification
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-11579
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11579
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 2.7.0
>            Reporter: Steve Loughran
>         Attachments: HDFS-7665.patch
>
>
> With the addition of a major new feature to filesystems, the filesystem specification
in hadoop-common/site is now out of sync. 
> This means that
> # there's no strict specification of what it should do
> # you can't derive tests from that specification
> # other people trying to implement the API will have to infer what to do from the HDFS
source
> # there's no way to decide whether or not the HDFS implementation does what it is intended.
> # without matching tests against the raw local FS, differences between the HDFS impl
and the Posix standard one won't be caught until it is potentially too late to fix.
> The operation should be relatively easy to define (after a truncate, the files bytes
[0...len-1] must equal the original bytes, length(file)==len, etc)
> The truncate tests already written could then be pulled up into contract tests which
any filesystem implementation can run against.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message