Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
1.8.0
Description
The current build configuration shades the AWS SDK into flink-s3-fs-hadoop.jar
Due to MSHAD-156 the shading itself does not only add the classes to the JAR but also alters the string literal PACKAGE_PREFIXES_TO_SHADE in org.apache.flink.fs.s3hadoop.S3FileSystemFactory from com.amazonaws. to org.apache.flink.fs.s3base.shaded.com.amazonaws - which causes settings like
fs.s3a.aws.credentials.provider: com.amazonaws.auth.DefaultAWSCredentialsProviderChain
to not be remapped properly as the startsWith in org.apache.flink.fs.s3.common.HadoopConfigLoader.shadeClassConfig() doesn't match the beginning of the FQCN.
This is a known issue in the Maven shade plugin (see MSHAD-156) - a possible workaround is named in the ticket, too.
This issue is only visible looking into the compiled class file after the shading happened!
Fixing the PACKAGE_PREFIXES_TO_SHADE value alone doesn't help as based on FLINK_SHADING_PREFIX the FQCN is assembled as
org.apache.flink.fs.s3hadoop.shaded.com.amazonaws.auth.DefaultAWSCredentialsProviderChain
which can't be found either;
the class is located at
org.apache.flink.fs.s3base.shaded.com.amazonaws.auth.DefaultAWSCredentialsProviderChain
Attachments
Issue Links
- is broken by
-
MSHADE-156 shade plugin is transforming also strings that are not supposed to be transformed
- Open
- relates to
-
FLINK-13602 S3 Presto filesystem effectively does not support credential providers
- Open
-
FLINK-8439 Add Flink shading to AWS credential provider s3 hadoop config
- Closed
- links to