[
https://issues.apache.org/jira/browse/HADOOP-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236965#comment-13236965
]
Todd Lipcon commented on HADOOP-8060:
-------------------------------------
Doing shallow conf comparison as part of the FS key seems a bit dangerous --
I'm guessing we'll end up with a lot of leakage issues in long running daemons
like the NM/RM.
Anyone else have some other ideas how to deal with this? I don't think the
CreateFlag idea is bad -- maybe better than futzing with the cache.
> 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
> Fix For: 0.23.2, 0.24.0
>
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
