[
https://issues.apache.org/jira/browse/HIVE-16047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993529#comment-15993529
]
Sergio Peña commented on HIVE-16047:
------------------------------------
Hey guys, [~ruili], [~ferdinand],
I think we should try to revert this from Hive if the method is expected to be
changed on maintenance Hadoop releases. Sometimes, we'd like to bump our Hadoop
supported version in maintenance releases as well, but if we do so, then we
might need to add more shims interfaces just for the isHDFSEncryptionEnabled
method in a Hive maintenance release.
[~lirui] You mentioned is ok to revert it on master, and work with the hdfs
team to provide some public API for this. Can we continue with this? Also, the
patch is not on branch-2.2 (next stable hive version), and branch-2.3 might be
a little unstable due to many changes going on this branch. Can we try to
revert it from branch-2 and branch-2.3?
> Shouldn't try to get KeyProvider unless encryption is enabled
> -------------------------------------------------------------
>
> Key: HIVE-16047
> URL: https://issues.apache.org/jira/browse/HIVE-16047
> Project: Hive
> Issue Type: Bug
> Reporter: Rui Li
> Assignee: Rui Li
> Priority: Minor
> Fix For: 2.2.0
>
> Attachments: HIVE-16047.1.patch, HIVE-16047.2.patch
>
>
> Found lots of following errors in HS2 log:
> {noformat}
> hdfs.KeyProviderCache: Could not find uri with key
> [dfs.encryption.key.provider.uri] to create a keyProvider !!
> {noformat}
> Similar to HDFS-7931
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
