You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Kihwal Lee (Created) (JIRA)" <ji...@apache.org> on 2012/02/12 01:01:28 UTC
[jira] [Created] (HADOOP-8060) Add a capability to use of
consistent checksums for append and copy
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.24.0, 0.23.1
Reporter: Kihwal Lee
Assignee: Kihwal Lee
Fix For: 0.24.0, 0.23.2
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
[jira] [Resolved] (HADOOP-8060) Add a capability to discover and
set checksum types per file.
Posted by "Kihwal Lee (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kihwal Lee resolved HADOOP-8060.
--------------------------------
Resolution: Fixed
> Add a capability to discover and set checksum types per file.
> -------------------------------------------------------------
>
> 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.3, 3.0.0, 2.2.0-alpha
>
>
> 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