You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Marco Nicosia (JIRA)" <ji...@apache.org> on 2008/03/17 17:15:24 UTC
[jira] Created: (HADOOP-3032) Remove distcp from hadoop core
libraries, and publish documentation
Remove distcp from hadoop core libraries, and publish documentation
-------------------------------------------------------------------
Key: HADOOP-3032
URL: https://issues.apache.org/jira/browse/HADOOP-3032
Project: Hadoop Core
Issue Type: Bug
Components: mapred
Reporter: Marco Nicosia
Priority: Critical
Every time we want to ship a change in distcp, not only do we have to replace the entire version of map-reduce deployed to the clusters, we also have to update internal documentation to reflect those changes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3032) Remove distcp from hadoop core
libraries, and publish documentation
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580574#action_12580574 ]
Owen O'Malley commented on HADOOP-3032:
---------------------------------------
I don't think this is a good plan. distcp is an important enough utility that it should be QA'ed and released with the rest of Hadoop. Having lots of versions of distcp running around a clustered sounds problematic.
> Remove distcp from hadoop core libraries, and publish documentation
> -------------------------------------------------------------------
>
> Key: HADOOP-3032
> URL: https://issues.apache.org/jira/browse/HADOOP-3032
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Marco Nicosia
> Priority: Critical
>
> Every time we want to ship a change in distcp, not only do we have to replace the entire version of map-reduce deployed to the clusters, we also have to update internal documentation to reflect those changes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.