Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-15620 Über-jira: S3A phase VI: Hadoop 3.3 features
  3. HADOOP-14762

S3A warning of obsolete encryption key which is never used

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 2.9.0
    • Fix Version/s: None
    • Component/s: fs/s3
    • Labels:
      None

      Description

      During CLI init, I get warned of using an obsolete file.

      ./hadoop s3guard import  s3a://hwdev-steve-ireland-new
      2017-08-11 18:08:43,935 DEBUG conf.Configuration: Reloading 3 existing configurations
      2017-08-11 18:08:45,146 INFO Configuration.deprecation: fs.s3a.server-side-encryption-key is deprecated. Instead, use fs.s3a.server-side-encryption.key
      2017-08-11 18:08:45,702 INFO s3guard.S3GuardTool: Metadata store DynamoDBMetadataStore{region=eu-west-1, tableName=hwdev-steve-ireland-new} is initialized.
      ./hadoop s3guard import  s3a://hwdev-steve-ireland-new
      2017-08-11 18:08:43,935 DEBUG conf.Configuration: Reloading 3 existing configurations
      2017-08-11 18:08:45,146 INFO Configuration.deprecation: fs.s3a.server-side-encryption-key is deprecated. Instead, use fs.s3a.server-side-encryption.key
      2017-08-11 18:08:45,702 INFO s3guard.S3GuardTool: Metadata store DynamoDBMetadataStore{region=eu-west-1, tableName=hwdev-steve-ireland-new} is initialized.
      ./hadoop s3guard import  s3a://hwdev-steve-ireland-new
      2017-08-11 18:08:43,935 DEBUG conf.Configuration: Reloading 3 existing configurations
      2017-08-11 18:08:45,146 INFO Configuration.deprecation: fs.s3a.server-side-encryption-key is deprecated. Instead, use fs.s3a.server-side-encryption.key
      2017-08-11 18:08:45,702 INFO s3guard.S3GuardTool: Metadata store DynamoDBMetadataStore{region=eu-west-1, tableName=hwdev-steve-ireland-new} is initialized.
      

      I don't have this setting set as far as I can see, not in an XML file nor any jceks file. Maybe its falsely being picked up during the scan for jceks files?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                stevel@apache.org Steve Loughran
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: