[
https://issues.apache.org/jira/browse/HADOOP-14104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907846#comment-15907846
]
Yongjun Zhang commented on HADOOP-14104:
----------------------------------------
Hi [~rushabh.shah],
Thanks for pointing it out. Because {{DFSClient#isHDFSEncryptionEnabled}} is a
public method of {{DFSClient}}, I thought anyone could call it including any
mapreduce task.
Not an ask for this jira, - we can do it later - If this method is only
intended to be called by {{DistributedFileSystem#addDelegationTokens}} and
{{DistributedFileSystem.getTrashRoot}}, maybe we can add a javadoc to indicate
that. BTW, One could create FsShell object and call shell from any java code
too, we can worry about that later.
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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
