[
https://issues.apache.org/jira/browse/HADOOP-11579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315877#comment-14315877
]
Hadoop QA commented on HADOOP-11579:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12698014/HADOOP-11579-01.patch
against trunk revision 7c6b654.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 2 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5653//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5653//artifact/patchprocess/newPatchFindbugsWarningshadoop-common.html
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5653//console
This message is automatically generated.
> 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
> Attachments: HADOOP-11579-01.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 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)
