[
https://issues.apache.org/jira/browse/HADOOP-11319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218413#comment-14218413
]
Tim Robertson commented on HADOOP-11319:
----------------------------------------
Thanks again, and that is a fair point about maintaining legacy code.
This is an honest question - when updating to later versions of Hadoop libs (or
a minor version in a distribution, such as CDH 5.2.x -> 5.3.x), isn't it
expected that applications will have to adapt somewhat? Especially when people
are relying on transitive dependencies, might it be enough to coach folks
towards using mvn dependency:analyze more rigorously?
Aside: we've worked through our problems and are about to go to production on
Yarn upgrading from MR1 and CDH4.3, but it was not without pain and a fair
amount of pom exclusions (logging, and unwanted MR1 things coming in),
downgrading libs (Jackson and Guava), setting user CP precedence working around
issues like https://issues.apache.org/jira/browse/OOZIE-2066.
> Update Guava to 18.0
> --------------------
>
> Key: HADOOP-11319
> URL: https://issues.apache.org/jira/browse/HADOOP-11319
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: build
> Reporter: Tim Robertson
> Priority: Critical
>
> In the hadoop libraries you'll find both 11.0.2 (test scope IIRC) and 14.0.1
> which are both very outdated. 14.0.1 removes things used in 11.0.2 and 15.0
> has removed things in use by Hadoop code in 14.0.1.
> In our experience through CDH3,4 and 5 Guava (along with Jackson and SLF4J
> 1.7.5) have been the biggest cause for CP issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
