[
https://issues.apache.org/jira/browse/HADOOP-11074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128616#comment-14128616
]
David S. Wang commented on HADOOP-11074:
----------------------------------------
Forgot to also mention that I changed the top-level pom.xml to add an exclusion
for jackson for aws-java-sdk, which has the dependency on the earlier version
of jackson. Moving to aws-java-sdk 1.8.9 didn't do the trick, and while it
would be great to harmonize the jackson dependency between aws-java-sdk and
azure, I don't see that happening anytime soon.
Colin, I filed a findbugs JIRA as HADOOP-11082 and linked it to this JIRA.
> Move s3-related FS connector code to hadoop-aws
> -----------------------------------------------
>
> Key: HADOOP-11074
> URL: https://issues.apache.org/jira/browse/HADOOP-11074
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.0.0
> Reporter: David S. Wang
> Assignee: David S. Wang
> Fix For: 3.0.0
>
> Attachments: HADOOP-11074.patch, HADOOP-11074.patch.2,
> HADOOP-11074.patch.3
>
>
> Now that hadoop-aws has been created, we should actually move the relevant
> code into that module, similar to what was done with hadoop-openstack, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
