incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (Commented) (JIRA)" <>
Subject [jira] [Commented] (BIGTOP-316) split up hadoop packages into common, hdfs, mapreduce (and yarn)
Date Thu, 29 Dec 2011 02:27:31 GMT


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:
>             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:!default.jspa
For more information on JIRA, see:


View raw message