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 "Yongjun Zhang (JIRA)" <ji...@apache.org> on 2017/03/27 23:00:45 UTC
[jira] [Comment Edited] (HADOOP-14104) Client should always ask
namenode for kms provider path.
[ https://issues.apache.org/jira/browse/HADOOP-14104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944191#comment-15944191 ]
Yongjun Zhang edited comment on HADOOP-14104 at 3/27/17 11:00 PM:
------------------------------------------------------------------
Thanks [~daryn] a lot for the review and comments.
Hi [~shahrs87],
Wonder if you have chance to look at Daryn's comments?
Many thanks!
was (Author: yzhangal):
Thanks [~daryn] a lot for the review and comments.
Hi [~rushabh.shah],
Wonder if you have chance to look at Daryn's comments?
Many thanks!
> 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
> Attachments: HADOOP-14104-trunk.patch, HADOOP-14104-trunk-v1.patch, HADOOP-14104-trunk-v2.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.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org