[jira] [Updated] (HDFS-4090) getFileChecksum() result incompatible when called against zero-byte files.
[ https://issues.apache.org/jira/browse/HDFS-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryn Sharp updated HDFS-4090: -- Resolution: Fixed Fix Version/s: 0.23.5 2.0.3-alpha 3.0.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) I've committed to trunk, branch-2, branch-23. Thanks Kihwal! 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 Fix For: 3.0.0, 2.0.3-alpha, 0.23.5 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
[jira] [Updated] (HDFS-4090) getFileChecksum() result incompatible when called against zero-byte files.
[ https://issues.apache.org/jira/browse/HDFS-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-4090: - Attachment: hdfs-4090.patch 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
[jira] [Updated] (HDFS-4090) getFileChecksum() result incompatible when called against zero-byte files.
[ https://issues.apache.org/jira/browse/HDFS-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-4090: - Status: Patch Available (was: Open) 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: 2.0.2-alpha, 0.23.4 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