[
https://issues.apache.org/jira/browse/HADOOP-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442514#comment-13442514
]
Kihwal Lee commented on HADOOP-8060:
------------------------------------
In HDFS-3177, Sanjay suggested that the one checksum type per file be enforced
architecturally, rather than DFSClient doing it using existing facility. The
changes in HDFS-3177 still allows DistCp, etc. to discover and set checksum
parameters so that the results of getFileChecksum() on copies can match. I will
resolve this jira with a modified summary. I expect Sanjay to file a new Jira
when he has a proposal.
> Add a capability to use of consistent checksums for append and copy
> -------------------------------------------------------------------
>
> Key: HADOOP-8060
> URL: https://issues.apache.org/jira/browse/HADOOP-8060
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs, util
> Affects Versions: 0.23.0, 0.23.1, 0.24.0
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
>
> After the improved CRC32C checksum feature became default, some of use cases
> involving data movement are no longer supported. For example, when running
> DistCp to copy from a file stored with the CRC32 checksum to a new cluster
> with the CRC32C set to default checksum, the final data integrity check fails
> because of mismatch in checksums.
--
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
