[
https://issues.apache.org/jira/browse/BIGTOP-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207797#comment-13207797
]
Arun C Murthy commented on BIGTOP-398:
--------------------------------------
Bruno, many thanks for your clarifications.
----
A couple points which would do away the last vestiges of my confusion:
Drawing the distinction between projects packaged & integrated by Apache Bigtop
(Hadoop, HBase, Pig, Hive, Oozie, Flume, etc.) and ones which are merely
transitive dependencies (protocolbuffers, clover, guava etc.), I'm coming away
understanding that:
# Apache Bigtop maybe choose to manipulate the upstream projects dependencies
(e.g. with flume-0.9.3) *iff* necessary. As you say, you don't patch the
upstream project tarball, but you may take the source and possibly manipulate
the build and/or runtime dependencies as was done with flume-0.9.3 for
bigtop-0.2.0. Correct?
# Apache Bigtop may choose to include ASF-compliant projects. What does that
mean? Are you merely talking about the ASL? Or, do you refer to actual projects
developed under the aegis of the ASF? If it's the former, including flume-0.9.3
(again, under the distinction I drew) in bigtop-0.2.0 was maybe just a one-off?
Thanks again for helping me understand Apache Bigtop, appreciate it.
> How does bigtop deal with flume dependency on CDH?
> --------------------------------------------------
>
> Key: BIGTOP-398
> URL: https://issues.apache.org/jira/browse/BIGTOP-398
> Project: Bigtop
> Issue Type: Bug
> Reporter: Arun C Murthy
> Assignee: Bruno Mahé
> Labels: cdh
>
> Currently flume (part of BigTop) depends on CDH components (thrift, zk,
> hadoop-core). How does Bigtop deal with this?
--
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
