[
https://issues.apache.org/jira/browse/HADOOP-14104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894822#comment-15894822
]
Rushabh S Shah commented on HADOOP-14104:
-----------------------------------------
Thanks [~daryn] [~andrew.wang] [~yzhangal] [~jojochuang] for the discussion and
reviews.
I will put up a patch in couple of days with test cases implementing Daryn's
idea from [this
comment|https://issues.apache.org/jira/browse/HADOOP-14104?focusedCommentId=15892979&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15892979].
We can then discuss further ahead.
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
