Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.23.0, 0.23.1, 0.24.0
-
None
Description
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.
Attachments
Issue Links
- incorporates
-
HDFS-3176 JsonUtil should not parse the MD5MD5CRC32FileChecksum bytes on its own.
- Closed
-
HDFS-3177 Allow DFSClient to find out and use the CRC type being used for a file.
- Closed
-
HADOOP-8239 Extend MD5MD5CRC32FileChecksum to show the actual checksum type being used
- Closed
-
HADOOP-8240 Allow users to specify a checksum type on create()
- Closed
- relates to
-
HDFS-3054 distcp -skipcrccheck has no effect
- Closed