Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 4571 invoked from network); 29 Aug 2008 23:30:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Aug 2008 23:30:40 -0000 Received: (qmail 86250 invoked by uid 500); 29 Aug 2008 23:30:33 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 86226 invoked by uid 500); 29 Aug 2008 23:30:33 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 86215 invoked by uid 99); 29 Aug 2008 23:30:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Aug 2008 16:30:33 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Aug 2008 23:29:43 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4C0F9234C1C5 for ; Fri, 29 Aug 2008 16:29:44 -0700 (PDT) Message-ID: <1942615851.1220052584310.JavaMail.jira@brutus> Date: Fri, 29 Aug 2008 16:29:44 -0700 (PDT) From: "Tsz Wo (Nicholas), SZE (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-3941) Extend FileSystem API to return file-checksums/file-digests In-Reply-To: <1891260826.1218582464584.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-3941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627146#action_12627146 ] Tsz Wo (Nicholas), SZE commented on HADOOP-3941: ------------------------------------------------ > Distcp should not hardwire any algorithm That is true. We might need a method for getting the supported algorithms of a file system. Algorithms will be sorted by the preference. For example, if S3 supports {MD5, FileLength}, HDFS supports {HDFS-Checksum, FileLength} and LocalFS supports {MD5, HDFS-Checksum, FileLength}, then - S3 -> HDFS or HDFS -> S3 will use FileLength - S3 -> S3 will use MD5 - S3 -> LocalFS will use MD5 - LocalFS -> HDFS will use HDFS-Checksum > Extend FileSystem API to return file-checksums/file-digests > ----------------------------------------------------------- > > Key: HADOOP-3941 > URL: https://issues.apache.org/jira/browse/HADOOP-3941 > Project: Hadoop Core > Issue Type: New Feature > Components: fs > Reporter: Tsz Wo (Nicholas), SZE > Assignee: Tsz Wo (Nicholas), SZE > Attachments: 3941_20080818.patch, 3941_20080819.patch, 3941_20080819b.patch, 3941_20080820.patch, 3941_20080826.patch, 3941_20080827.patch > > > Suppose we have two files in two locations (may be two clusters) and these two files have the same size. How could we tell whether the content of them are the same? > Currently, the only way is to read both files and compare the content of them. This is a very expensive operation if the files are huge. > So, we would like to extend the FileSystem API to support returning file-checksums/file-digests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.