[
https://issues.apache.org/jira/browse/BIGTOP-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176865#comment-13176865
]
Matt Foley commented on BIGTOP-316:
-----------------------------------
Cos, I don't think I deserve the aggressive response. Please re-read my
comment. I specifically did not say that we should remain with a monolithic
packaging, and in fact explicitly said letting people experiment with mixing
and matching was welcome. "According to my logic", I have only expressed a
requirement to be able to readily identify when someone ignorant has
mixed-and-matched something they shouldn't have -- because I think it is likely
to happen a LOT in the field.
Regarding package dependencies being an adequate solution: I see that they
would support my first concern - "give me the version 1.0.0 of all packages" -
I suppose by defining a super-package dependent on all the right versioned
sub-components. However, if the user is trying to experiment with
mix-and-match, then they can't use that super-package, because it will enforce
the monolithic versioning, right? So they'll install the bits and pieces
individually. How do we (a) make sure they get all the pieces they need, and
(b) identify which pieces are mis-fits if the net result doesn't work?
BTW, if you are thinking that all the sub-components can be given dependencies
that make it impossible to install them with other sub-components that don't
meet their needs, I don't buy it. There's no way you're going to successfully
do that while also maintaining the goal to allow mix-and-match experimentation;
the result will be over-constrained and meet neither goal well.
> 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
