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 "Sean Busbey (JIRA)" <ji...@apache.org> on 2019/01/29 18:50:00 UTC
[jira] [Commented] (HADOOP-15387) Produce a shaded
hadoop-cloud-storage JAR for applications to use
[ https://issues.apache.org/jira/browse/HADOOP-15387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16755284#comment-16755284 ]
Sean Busbey commented on HADOOP-15387:
--------------------------------------
[~stevel@apache.org] can you help me on understanding scope here a bit?
I think what the description says is we end up with a single jar where all classes are in {{org.apache.hadoop}} or {{software.amazon.awssdk}} and we rely on shading to relocate any others (modulo the normal caveats on logging / tracing libraries that came up during the hadoop-client modules).
Does it need to be all of the Amazon AWS SDK? Is there some interface jar that we could use while allowing BYO-SDK? Or for that matter could we just update the various cloud storage modules to individually relocate things that aren't either hadoop-client-facing or their respective service's SDK?
> Produce a shaded hadoop-cloud-storage JAR for applications to use
> -----------------------------------------------------------------
>
> Key: HADOOP-15387
> URL: https://issues.apache.org/jira/browse/HADOOP-15387
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs/adl, fs/azure, fs/oss, fs/s3, fs/swift
> Affects Versions: 3.1.0
> Reporter: Steve Loughran
> Priority: Major
>
> Produce a maven-shaded hadoop-cloudstorage JAR for dowstream use so that
> * Hadoop dependency choices don't control their decisions
> * Little/No risk of their JAR changes breaking Hadoop bits they depend on
> This JAR would pull in the shaded hadoop-client JAR, and the aws-sdk-bundle JAR, neither of which would be unshaded (so yes, upgrading aws-sdks would be a bit risky, but double shading a pre-shaded 30MB JAR is excessive on multiple levels.
> Metrics of success: Spark, Tez, Flink etc can pick up and use, and all are happy
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org