Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 19 Oct 2012 21:30:13 +0000 (UTC)
From: "Kihwal Lee (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <820793369.3143.1350682213514.JavaMail.jiratomcat@arcas>
In-Reply-To: <1954501559.3142.1350682213427.JavaMail.jiratomcat@arcas>
Subject: [jira] [Assigned] (HDFS-4090) getFileChecksum() result incompatible
 when called against zero-byte files.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kihwal Lee reassigned HDFS-4090:
--------------------------------

    Assignee: Kihwal Lee
    
> 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
>
> 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