[
https://issues.apache.org/jira/browse/HDFS-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003001#comment-16003001
]
Naveen Gangam commented on HDFS-11687:
--------------------------------------
[~eddyxu] Seems like we have come full circle with this fix. Prior to
HIVE-16047, hive code was already using the {{getKeyProvider}} API. However,
each time it was called when encryption was disabled, there was a recurring
message in HiveServer logs about {{hdfs.KeyProviderCache: Could not find uri
with key [dfs.encryption.key.provider.uri] to create a keyProvider !!}} . The
goal of HIVE-16047 was to address this log message.
So the fix included a call to {{DFSClient.isHDFSEncryptionEnabled()}}, which is
now deleted in favor of {{HdfsAdmin.getKeyProvider()}} which appears to use the
same underlying {{getKeyProvider()}}. Wouldnt we see the same log message again
if we use {{HdfsAdmin.getKeyProvider()}} ? Thanks
> Add new public encryption APIs required by Hive
> -----------------------------------------------
>
> Key: HDFS-11687
> URL: https://issues.apache.org/jira/browse/HDFS-11687
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: encryption
> Affects Versions: 2.6.5
> Reporter: Andrew Wang
> Assignee: Lei (Eddy) Xu
> Fix For: 2.9.0, 3.0.0-alpha3
>
> Attachments: HDFS-11687.00.patch, HDFS-11687.01.patch,
> HDFS-11687.02.patch, HDFS-11687.03.patch
>
>
> As discovered on HADOOP-14333, Hive is using reflection to get a DFSClient
> for its encryption shim. We should provide proper public APIs for getting
> this information.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
