Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <973397031.1252424997483.JavaMail.jira@brutus>
Date: Tue, 8 Sep 2009 08:49:57 -0700 (PDT)
From: "Ravi Gummadi (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-644) distcp does not skip copying file
 if we are updating single file
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752582#action_12752582 ] 

Ravi Gummadi commented on MAPREDUCE-644:
----------------------------------------

I tested it manually and I see that the single file's copy is skipped only with the patch.

Am wondering if we can verify the count of files copied(there is a counter 'COPY' in distcp for this) from testcase after running distcp for a single file with -update option and the destination contains the file already.
Thoughts ?

> distcp does not skip copying file if we are updating single file
> ----------------------------------------------------------------
>
>                 Key: MAPREDUCE-644
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-644
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: distcp
>            Reporter: Ravi Gummadi
>            Assignee: Ravi Gummadi
>         Attachments: d_singlefile_update.patch
>
>
> distcp doesn't skip copying file when we do -update on single file if the destfile already exists.
> When we do 
> hadoop distcp -update srcfilename destfilename
> it seems to be comparing checksums of srcfilename and destfilename/srcfilename and so skip is not done. It should compare checksums of srcfilename and destfilename.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.