[
https://issues.apache.org/jira/browse/BIGTOP-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002523#comment-14002523
]
Roman Shaposhnik commented on BIGTOP-1109:
------------------------------------------
Two ways to answer this question:
# it may not be a problem today (haven't checked) with 0.8.0 BOM moving to
latest component versions
# it is still a problem in general in that all of the dependency jars that
are shipped by Hadoop need to be harmonized with the rest of Hadoop ecosystem
> Remove protobuf jar from a few packages that depend on Hadoop
> -------------------------------------------------------------
>
> Key: BIGTOP-1109
> URL: https://issues.apache.org/jira/browse/BIGTOP-1109
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.7.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.8.0
>
>
> Turns out a few of Bigtop packages ship an extra copy of protobuf. Given that
> the master copy should always come from Hadoop's classpath we can safely
> remove the other one. It'll also cut down on cases where protobuf of the
> component gets out of synch with the one Hadoop is using.
> Here's the current list:
> {noformat}
> /usr/lib/oozie/libtools/protobuf-java-2.5.0.jar
> /usr/lib/spark/lib/protobuf-java-2.4.1.jar
> /usr/lib/hbase/lib/protobuf-java-2.4.0a.jar
> /usr/lib/flume/lib/protobuf-java-2.4.1.jar
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
