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

Doug Cutting commented on HADOOP-7624:
--------------------------------------

Allen, are all of these choices equally acceptable to you?  If not, what is 
your preferred choice?

Some questions about each of these choices:

a. Are you proposing that things that are currently in various contrib 
directories move to the hadoop-tools module created by this proposal?  If so, 
those sound like good follow-on issues to file.

b. Where specifically in the current tree would you prefer we place the new 
distcp code (MAPREDUCE-2765)? In hadoop-mapreduce-project/src/tools, beside the 
old distcp?

c. Will you propose and drive a new subproject?  Would the release cycle be 
separate from Hadoop?

d. Distcp is not currently in contrib.  Would you prefer that the new version 
be committed in hadoop-mapreduce-project/src/contrib?

e. I think that's what's proposed here.  The 'rules and process' are not 
currently formalized.  Rather it was agreed that we should be more cautious 
than before about accepting things and that we be more aggressive about booting 
things when they're abandoned and/or stop passing tests.  If you'd like to 
formalize this and build consensus around some rules and process that'd be 
great.  Should we block the commit of MAPREDUCE-2765 on that?


> Set things up for a top level hadoop-tools module
> -------------------------------------------------
>
>                 Key: HADOOP-7624
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7624
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Alejandro Abdelnur
>         Attachments: HADOOP-7624.patch
>
>
> See this thread: http://markmail.org/thread/cxtz3i6lvztfgfxn
> We need to get things up and running for a top level hadoop-tools module. 
> DistCpV2 will be the first resident of this new home. Things we need:
>  - The module itself and a top level pom with appropriate dependencies
>  - Integration with the patch builds for the new module
>  - Integration with the post-commit and nightly builds for the new module.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to