[
https://issues.apache.org/jira/browse/MAPREDUCE-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614325#comment-13614325
]
Suresh Srinivas commented on MAPREDUCE-5081:
--------------------------------------------
This is a large patch. All the new code that is added in this patch, I compared
with the trunk version of the files and found very little changes. These
changes are mainly related method changes and going back to old ways of doing
things.
Comments:
# sslConfig.xml, distcp-default.xml is missing Apache license header.
# There is a lot difference in DistCp.java in trunk and DistCp.java in this
patch?
# I have concerns about replacing existing distcp with new distcp2. Would this
have some behavior that could make the tool behave in a way that could be
deemed incompatible by existing users. Why not leave the old distcp as is and
add a new command for distcp2?
> 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,
> m5981_20130323.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
> - distcp part of HADOOP-8341: Fix findbugs issues in hadoop-tools
> - MAPREDUCE-5014: custom CopyListing
--
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
