You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/04/19 11:48:42 UTC
[jira] [Created] (HADOOP-14324) Switch to
fs.s3a.server-side-encryption.key as property for encryption secret
Steve Loughran created HADOOP-14324:
---------------------------------------
Summary: Switch to fs.s3a.server-side-encryption.key as property for encryption secret
Key: HADOOP-14324
URL: https://issues.apache.org/jira/browse/HADOOP-14324
Project: Hadoop Common
Issue Type: Sub-task
Components: fs/s3
Reporter: Steve Loughran
Priority: Blocker
Before this ships, can we rename {{fs.s3a.server-side-encryption-key}} to {{fs.s3a.server-side-encryption.key}}.
This makes it consistent with all other .key secrets in S3A. so
* simplifies documentation
* reduces confusion "is it a - or a ."? This confusion is going to surface in config and support
I know that CDH is shipping with the old key, but it'll be easy for them to add a deprecation property to handle the migration. I do at least what the ASF release to be stable before it ships.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org