[
https://issues.apache.org/jira/browse/HADOOP-14104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rushabh S Shah updated HADOOP-14104:
------------------------------------
Description:
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.
was:
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.
> 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: Bug
> Components: kms
> Reporter: Rushabh S Shah
> Assignee: Rushabh S Shah
>
> 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]
