[
https://issues.apache.org/jira/browse/HIVE-16047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15979144#comment-15979144
]
Andrew Wang commented on HIVE-16047:
------------------------------------
Honestly, I think the best thing to here is to revert. The fallback to config
detection is also brittle, since the point of the Hadoop change that broke this
was to query the KMS URI from the NameNode rather than config. Hive has limited
ability here to fix what is ultimately an Hadoop-level problem.
We'll work to quash this log message in Hadoop, I don't know why it's logged at
ERROR, or at all really. HDFS-7931 was an incomplete fix.
> 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)
