hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laurent Goujon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-10295) Allow distcp to automatically identify the checksum type of source files and use it for the target
Date Tue, 28 Jan 2014 06:58:38 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Laurent Goujon updated HADOOP-10295:
------------------------------------

    Attachment: hadoop-10295.patch

Alternative patch to implement the requested feature. It extends the current list of file
attributes option with a checksum attribute.

It requires two other patches to be applied first in order to compile and tests to pass:
* HADOOP-10294 : FileChecksum should provide getChecksumOpt method
* HDFS-5843: DFSClient.getFileChecksum() throws IOException if checksum is disabled

> Allow distcp to automatically identify the checksum type of source files and use it for
the target
> --------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-10295
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10295
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 2.2.0
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>         Attachments: HADOOP-10295.000.patch, hadoop-10295.patch
>
>
> Currently while doing distcp, users can use "-Ddfs.checksum.type" to specify the checksum
type in the target FS. This works fine if all the source files are using the same checksum
type. If files in the source cluster have mixed types of checksum, users have to either use
"-skipcrccheck" or have checksum mismatching exception. Thus we may need to consider adding
a new option to distcp so that it can automatically identify the original checksum type of
each source file and use the same checksum type in the target FS. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message