[HADOOP-16986] s3a to not need wildfly on the classpath - ASF JIRA

Voters

Watch issue

Watchers

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Target Version/s:

3.3.1
Release Note:

Hide
hadoop-aws can use native openssl libraries for better HTTPS performance -consult the S3A performance document for details.

To enable this, wildfly.jar is declared as a compile-time dependency of the hadoop-aws module, so ensuring it ends up on the classpath of the hadoop command line, distribution packages and downstream modules.

It is however, still optional, unless fs.s3a.ssl.channel.mode is set to openssl

Show
hadoop-aws can use native openssl libraries for better HTTPS performance -consult the S3A performance document for details. To enable this, wildfly.jar is declared as a compile-time dependency of the hadoop-aws module, so ensuring it ends up on the classpath of the hadoop command line, distribution packages and downstream modules. It is however, still optional, unless fs.s3a.ssl.channel.mode is set to openssl

remove a hard dependency on wildfly.jar being on the classpath for S3; it's used if present, but handled if not
even if openssl is requested
and NPEs are caught and swallowed in case wildfly 1.0.4.Final ever gets on the classpath again