[
https://issues.apache.org/jira/browse/HADOOP-14104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16146410#comment-16146410
]
Junping Du commented on HADOOP-14104:
-------------------------------------
The patch cause incompatible API change here as omit previous constructor of
FsServerDefaults which is a public API. Just filed HADOOP-14814 and put up a
fix there. Please help to review and commit/fix this issue.
> Client should always ask namenode for kms provider path.
> --------------------------------------------------------
>
> Key: HADOOP-14104
> URL: https://issues.apache.org/jira/browse/HADOOP-14104
> Project: Hadoop Common
> Issue Type: Improvement
> Components: kms
> Reporter: Rushabh S Shah
> Assignee: Rushabh S Shah
> Fix For: 2.9.0, 3.0.0-alpha4, 2.8.2
>
> Attachments: HADOOP-14104-branch-2.8.patch,
> HADOOP-14104-branch-2.patch, HADOOP-14104-trunk.patch,
> HADOOP-14104-trunk-v1.patch, HADOOP-14104-trunk-v2.patch,
> HADOOP-14104-trunk-v3.patch, HADOOP-14104-trunk-v4.patch,
> HADOOP-14104-trunk-v5.patch
>
>
> According to current implementation of kms provider in client conf, there can
> only be one kms.
> In multi-cluster environment, if a client is reading encrypted data from
> multiple clusters it will only get kms token for local cluster.
> Not sure whether the target version is correct or not.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
