[
https://issues.apache.org/jira/browse/HADOOP-12527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384409#comment-15384409
]
Ben McCann commented on HADOOP-12527:
-------------------------------------
Going from Avro 1.7.4 to Avro 1.7.6 or 1.7.7 bumps Jackson from 1.8.x to 1.9.x.
This should be a no-op though because Hadoop is already using Jackson 1.9.x.
Going to Avro 1.8.1 bumps paranamer from 2.3 to 2.7 and commons-compress from
1.4.1 to 1.8.1. It also adds dependencies on xz 1.5 and joda-time 2.7.
Given that there's essentially no transitive dependency changes from bumping
Avro to 1.7.7 and that bumping Avro is a low risk upgrade, could we upgrade to
1.7.7 at least?
> Upgrade Avro dependency to 1.7.7 or later
> -----------------------------------------
>
> Key: HADOOP-12527
> URL: https://issues.apache.org/jira/browse/HADOOP-12527
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Affects Versions: 2.7.1
> Reporter: Jonathan Kelly
>
> Hadoop has depended upon Avro 1.7.4 for a couple of years now (see
> HADOOP-9672), but Apache Spark depends upon what is currently the latest
> version of Avro (1.7.7).
> This can cause issues if Spark is configured to include the full Hadoop
> classpath, as the classpath would then contain both Avro 1.7.4 and 1.7.7,
> with the 1.7.4 classes possibly winning depending on ordering. Here is an
> example of this issue:
> http://stackoverflow.com/questions/33159254/avro-error-on-aws-emr/33403111#33403111
> Would it be possible to upgrade Hadoop's Avro dependency to 1.7.7 now?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
