hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohini Palaniswamy (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8239) Extend MD5MD5CRC32FileChecksum to show the actual checksum type being used
Date Tue, 10 Apr 2012 16:23:16 GMT

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

Rohini Palaniswamy commented on HADOOP-8239:

When you fix this jira, can you add public getter methods for getting
bytesPerCRC, crcPerBlock, checksum and checksumType in MD5MD5CRC32FileChecksum?

We have internal tool/library that mimics the computation of the
hdfs checksum for a file downloaded to local filesystems (NFS/Linux filesystem).
This is for customers to validate the checksum of the file after they downloaded it to
other filesystems from hdfs via http(hdfsproxy). Since those fields were not accessible, wrote
a wrapper that
parses the MD5MD5CRC32FileChecksum bytes on its own similar to JsonUtil
(HDFS-3176). If there were public getter methods available it would help get
rid of the wrapper class. 
> Extend MD5MD5CRC32FileChecksum to show the actual checksum type being used
> --------------------------------------------------------------------------
>                 Key: HADOOP-8239
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8239
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>            Reporter: Kihwal Lee
>            Assignee: Kihwal Lee
>             Fix For: 0.23.3, 2.0.0, 3.0.0
> In order to support HADOOP-8060, MD5MD5CRC32FileChecksum needs to be extended to carry
the information on the actual checksum type being used. The interoperability between the extended
version and branch-1 should be guaranteed when Filesystem.getFileChecksum() is called over
hftp, webhdfs or httpfs.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message