You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2016/10/06 23:55:20 UTC
[jira] [Updated] (HADOOP-13692) hadoop-aws should declare explicit
dependency on Jackson 2 jars to prevent classpath conflicts.
[ https://issues.apache.org/jira/browse/HADOOP-13692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Nauroth updated HADOOP-13692:
-----------------------------------
Status: Patch Available (was: Open)
> hadoop-aws should declare explicit dependency on Jackson 2 jars to prevent classpath conflicts.
> -----------------------------------------------------------------------------------------------
>
> Key: HADOOP-13692
> URL: https://issues.apache.org/jira/browse/HADOOP-13692
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Priority: Minor
> Attachments: HADOOP-13692-branch-2.001.patch
>
>
> If an end user's application has a dependency on hadoop-aws and no other Hadoop artifacts, then it picks up a transitive dependency on Jackson 2.5.3 jars through the AWS SDK. This can cause conflicts at deployment time, because Hadoop has a dependency on version 2.2.3, and the 2 versions are not compatible with one another. We can prevent this problem by changing hadoop-aws to declare explicit dependencies on the Jackson artifacts, at the version Hadoop wants.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org