[
https://issues.apache.org/jira/browse/HADOOP-14324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Zhuge updated HADOOP-14324:
--------------------------------
Attachment: HADOOP-14324-branch-2-002.patch
Your patch suffers the same issue described in
https://issues.apache.org/jira/browse/HADOOP-14038?focusedCommentId=15905605&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15905605.
To reproduce, add the deprecated key {{fs.s3a.server-side-encryption-key}} to
{{core-site.xml}}, and run {{hadoop fs
-Dfs.s3a.server-side-encryption-algorithm=SSE-C -cat s3a://sse-c-file}}.
To fix, call {{Configuration.reloadExistingConfigurations}} at end of
{{addDeprecatedKeys}}.
I uploaded patch 002 with the fix and conflicts caused by my HADOOP-14241
resolved.
> 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
> Affects Versions: 2.9.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Blocker
> Attachments: HADOOP-14324-branch-2-001.patch,
> HADOOP-14324-branch-2-002.patch
>
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
