incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Mahé (Issue Comment Edited) (JIRA) <j...@apache.org>
Subject [jira] [Issue Comment Edited] (BIGTOP-316) split up hadoop packages into common, hdfs, mapreduce (and yarn)
Date Wed, 28 Dec 2011 23:13:32 GMT

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

Bruno Mahé edited comment on BIGTOP-316 at 12/28/11 11:12 PM:
--------------------------------------------------------------

Matt, I believe Roman was aiming at contributors being able to mix and match versions, not
really users. I don't see how users would be able to do so and I personnaly see Bigtop as
a coherent stack instead of a kit to build stacks (although nothing prevent anyone from selecting
their own favourite downstream versions).
Even if Bigtop components would not specify any dependencies, there would still be some work
needed to make sure components compile against each others (for instance, doing a maven build
on hbase, would pull hadoop from its default profile, not the one we want to exercise, so
the way a component is built may have to be tweaked) as well as testing their integration.
But mix-matching is only one of many benefits of such proposal.

                
      was (Author: bmahe):
    Matt, I believe Roman was aiming at contributors being able to mix and match versions,
not really users. I don't see how users would be able to do so and I personnaly see Bigtop
as a coherent stack instead of a kit to build stacks (although nothing prevent anyone from
selecting their own favourite downstream versions).
Even if Bigtop would not specify any version in its dependencies sections, there would still
be  work needed to make sure components compile against each others (for instance, doing a
maven build on hbase, would pull hadoop from its default profile, not the one we want to exercise,
so the way a component is built may have to be tweaked) as well as testing their integration.
But mix-matching is only one of many benefits of such proposal.

                  
> 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

       

Mime
View raw message