[
https://issues.apache.org/jira/browse/HDFS-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13480514#comment-13480514
]
Hadoop QA commented on HDFS-4090:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12550084/hdfs-4090.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) 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-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/3372//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3372//console
This message is automatically generated.
> getFileChecksum() result incompatible when called against zero-byte files.
> --------------------------------------------------------------------------
>
> Key: HDFS-4090
> URL: https://issues.apache.org/jira/browse/HDFS-4090
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs client
> Affects Versions: 0.23.4, 2.0.2-alpha
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Priority: Critical
> Attachments: hdfs-4090.patch
>
>
> When getFileChecksum() is called against a zero-byte file, the branch-1
> client returns MD5MD5CRC32FileChecksum with crcPerBlock=0, bytePerCrc=0 and
> md5=70bc8f4b72a86921468bf8e8441dce51, whereas a null is returned in trunk.
> The null makes sense since there is no actual block checksums, but this
> breaks the compatibility when doing distCp and calling getFileChecksum() via
> webhdfs or hftp.
> This JIRA is to make the client to return the same 'magic' value that the
> branch-1 and earlier clients return.
--
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
