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

Tsz Wo (Nicholas), SZE commented on MAPREDUCE-5081:
---------------------------------------------------

{noformat}
     [exec] -1 overall.  
     [exec] 
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec] 
     [exec]     +1 tests included.  The patch appears to include 41 new or 
modified tests.
     [exec] 
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning 
messages.
     [exec] 
     [exec]     +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
     [exec] 
     [exec]     -1 findbugs.  The patch appears to introduce 17 new Findbugs 
(version 1.3.9) warnings.
{noformat}
The remaining findbugs warnings are not related to this.
                
> Backport DistCpV2 and the related JIRAs to branch-1
> ---------------------------------------------------
>
>                 Key: MAPREDUCE-5081
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5081
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: distcp
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Tsz Wo (Nicholas), SZE
>         Attachments: m5981_20130321b.patch, m5981_20130321.patch
>
>
> Here is a list of DistCpV2 JIRAs:
> - MAPREDUCE-2765: DistCpV2 main jira
> - HADOOP-8703: turn CRC checking off for 0 byte size 
> - HDFS-3054: distcp -skipcrccheck has no effect.
> - HADOOP-8431: Running distcp without args throws IllegalArgumentException
> - HADOOP-8775: non-positive value to -bandwidth
> - MAPREDUCE-4654: TestDistCp is ignored
> - HADOOP-9022: distcp fails to copy file if -m 0 specified
> - HADOOP-9025: TestCopyListing failing
> - MAPREDUCE-5075: DistCp leaks input file handles
> - MAPREDUCE-5014: custom CopyListing (not yet committed to trunk)

--
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

Reply via email to