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

Eli Collins commented on BIGTOP-316:
------------------------------------

I think the description and discussion make this change sound like a much 
bigger deal than it actually is.  The motivations is that the packages should 
be updated to reflect the project split. Eg we should be able to install hdfs 
w/o mapreduce, or hdfs w/o yarn, or yarn w/o mapreduce (now that MR is 
user-side there's no reason to install it on all the servers right?), etc.

Currently there is one hadoop spec file that results in a bunch of hadoop 
packages (hadoop-<version>, hadoop-datanode, hadooop-namenode, 
hadoop-jobtracker, etc) where most packages depend on the primary 
hadoop-<version> package and introduce just service-specific bits (eg a 
datanode service script). What this change is proposing is that instead of a 
bunch of hadoop-* packages we subdivide into  common, hdfs,  mapreduce, and 
yarn packages.  Note that there is still a single coherent set of packages for 
a given bigtop release. We'll enforce this with version dependencies the same 
we do today to make sure hadoop-datanode depends the right hadoop-version, and 
eg hbase package x depends on zookeeper package x, ie this doesn't allow for 
arbitrary mixing and matching, it just updates the package structure to reflect 
the project split.
                
> split up hadoop packages into common, hdfs, mapreduce (and yarn)
> ----------------------------------------------------------------
>
>                 Key: BIGTOP-316
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-316
>             Project: Bigtop
>          Issue Type: Sub-task
>          Components: General
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.3.0
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to