Steve Loughran created HADOOP-18371: ---------------------------------------
Summary: s3a FS init logs at warn if fs.s3a.create.storage.class is unset Key: HADOOP-18371 URL: https://issues.apache.org/jira/browse/HADOOP-18371 Project: Hadoop Common Issue Type: Sub-task Components: fs/s3 Affects Versions: 3.3.9 Reporter: Steve Loughran Assignee: Monthon Klongklaew if you don't have an s3a storage class set in {{fs.s3a.create.storage.class}}, then whenever you create an S3A FS instance, it logs at warn {code} bin/hadoop s3guard bucket-info $BUCKET 2022-07-27 11:53:11,239 [main] INFO Configuration.deprecation (Configuration.java:logDeprecation(1459)) - fs.s3a.server-side-encryption.key is deprecated. Instead, use fs.s3a.encryption.key 2022-07-27 11:53:11,240 [main] INFO Configuration.deprecation (Configuration.java:logDeprecation(1459)) - fs.s3a.server-side-encryption-algorithm is deprecated. Instead, use fs.s3a.encryption.algorithm 2022-07-27 11:53:11,396 [main] WARN s3a.S3AFileSystem (S3AFileSystem.java:createRequestFactory(1004)) - Unknown storage class property fs.s3a.create.storage.class: ; falling back to default storage class 2022-07-27 11:53:11,839 [main] INFO impl.DirectoryPolicyImpl (DirectoryPolicyImpl.java:getDirectoryPolicy(189)) - Directory markers will be kept Filesystem s3a://stevel-london Location: eu-west-2 {code} note, this is why part of quaifying an sdk update involves looking at the logs and running the CLI commands by hand...you see if new messages have crept in -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org