[ https://issues.apache.org/jira/browse/HADOOP-18160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17507553#comment-17507553 ]
Steve Loughran commented on HADOOP-18160: ----------------------------------------- got a PR? the other possibility would be for that binding code to take either shaded or unshaded, but i suspect the maven shade plugin would cause grief here from remapping strings used in loadClass > `org.wildfly.openssl` should not be shaded by Hadoop build > ---------------------------------------------------------- > > Key: HADOOP-18160 > URL: https://issues.apache.org/jira/browse/HADOOP-18160 > Project: Hadoop Common > Issue Type: Bug > Components: build > Affects Versions: 3.3.1 > Environment: hadoop 3.3.1 > spark 3.2.1 > JDK8 > Reporter: André F. > Priority: Minor > > `org.wildfly.openssl` is a runtime library and its references are being > shaded on Hadoop, breaking the integration with other frameworks like Spark, > whenever the "fs.s3a.ssl.channel.mode" is set to "openssl". The error > produced in this situation is: > {code:java} > Suppressed: java.lang.NoClassDefFoundError: > org/apache/hadoop/shaded/org/wildfly/openssl/OpenSSLProvider{code} > Whenever it tries to be instantiated from the `DelegatingSSLSocketFactory`. > Spark tries to add it to its classpath without the shade, thus creating this > issue. > Dependencies which are not on "compile" scope should probably not be shaded > to avoid this kind of integration issues. > -- This message was sent by Atlassian Jira (v8.20.1#820001) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org