hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11579) Documentation for truncate
Date Thu, 12 Feb 2015 12:31:19 GMT

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

Hudson commented on HADOOP-11579:

SUCCESS: Integrated in Hadoop-Yarn-trunk #836 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/836/])
HADOOP-11579. Documentation for truncate. Contributed by Konstantin Shvachko. (shv: rev 6f6737b3bfda0f5c0b0a508dc8523f6636f3f4ab)
* hadoop-common-project/hadoop-common/src/site/markdown/FileSystemShell.md
* hadoop-common-project/hadoop-common/CHANGES.txt
* hadoop-common-project/hadoop-common/src/site/markdown/filesystem/filesystem.md

> Documentation for truncate
> --------------------------
>                 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
>            Assignee: Konstantin Shvachko
>             Fix For: 2.7.0
>         Attachments: HADOOP-11579-01.patch, HADOOP-11579-branch-2.patch, 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
> # 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

View raw message