incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Foley (Commented) (JIRA)" <>
Subject [jira] [Commented] (BIGTOP-316) split up hadoop packages into common, hdfs, mapreduce (and yarn)
Date Wed, 28 Dec 2011 08:11:31 GMT


Matt Foley commented on BIGTOP-316:

One of the benefits of monolithic packages is that you know the set of bits within is claimed
to be self-consistent.  If that is split up into many packages, then I would like to at least
be able to say "give me the version 1.0.0 of all packages", and easily get them.  Furthermore,
I need to be able to look at an installed system (in the field) and say, "yes, all the pieces
are version 1.0.0" -- or alternatively, "here's the problem:  this piece is only version 0.20.204,
but the other pieces are version 1.0.0, and that's not compatible."

While people are welcome to experiment with mix-and-match, it's going to be a minefield of
late-found problems in the field.  Let's do whatever is necessary to make it easy to spot
when mix-and-match has been attempted.  How do we address this?  Can a naming convention for
the piece-wise packages help address the problem?
> 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