[
https://issues.apache.org/jira/browse/SPARK-23654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16398653#comment-16398653
]
Steve Loughran commented on SPARK-23654:
----------------------------------------
# In Hadoop 3.x anyone trying to create an s3n client is told to upgrade to the
s3a connector; without that code snippet callers will get a class not found
exception, which may lull them into thinking its fixable.
# spark-kinesis declares a "provided dependency on the jar. If it really needs
it, it would make sense to scope it to compile, and at least remove it from the
main spark-core transient dependency list.
> cut jets3t as a dependency of spark-core; exclude it from hadoop-cloud module
> as incompatible
> ---------------------------------------------------------------------------------------------
>
> Key: SPARK-23654
> URL: https://issues.apache.org/jira/browse/SPARK-23654
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 2.4.0
> Reporter: Steve Loughran
> Priority: Minor
>
> Spark core declares a dependency on Jets3t, which pulls in other cruft
> # the hadoop-cloud module pulls in the hadoop-aws module with the
> jets3t-compatible connectors, and the relevant dependencies: the spark-core
> dependency is incomplete if that module isn't built, and superflous or
> inconsistent if it is.
> # We've cut out s3n/s3 and all dependencies on jets3t entirely from hadoop
> 3.x in favour we're willing to maintain.
> JetS3t was wonderful when it came out, but now the amazon SDKs massively
> exceed it in functionality, albeit at the expense of week-to-week stability
> and JAR binary compatibility
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
