[
https://issues.apache.org/jira/browse/HADOOP-12527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384565#comment-15384565
]
Steve Loughran commented on HADOOP-12527:
-----------------------------------------
"jackson' is a word to bring fear into the upgrade path. It sounds like moving
up to Avro 1.7.7 is OK for Hadoop 2.8. Avro 1.8 sounds more traumatic all
round. Joda time has had problems with Java versions, if it gets pulled into
more than just hadoop-aws then we should start by managing it explicitly
> 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
