You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Brock Noland (JIRA)" <ji...@apache.org> on 2014/08/11 23:58:13 UTC
[jira] [Comment Edited] (HIVE-7682) HadoopThriftAuthBridge20S
should not reset configuration unless required
[ https://issues.apache.org/jira/browse/HIVE-7682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14093237#comment-14093237 ]
Brock Noland edited comment on HIVE-7682 at 8/11/14 9:57 PM:
-------------------------------------------------------------
One work around is to check to see if the current UGI is configured for the requested authentication type (UserGroupInformation.getCurrentUser().getAuthenticationMethod()) and not create a new Configuration object if the current authentication type is the same as what the UGI is configured with.
was (Author: brocknoland):
One work around is to check to see if the current UGI is configured for the requested authentication type (UserGroupInformation.getCurrentUser().getAuthenticationMethod();) and not create a new Configuration object if the current authentication type is the same as what the UGI is configured with.
> HadoopThriftAuthBridge20S should not reset configuration unless required
> ------------------------------------------------------------------------
>
> Key: HIVE-7682
> URL: https://issues.apache.org/jira/browse/HIVE-7682
> Project: Hive
> Issue Type: Bug
> Reporter: Brock Noland
> Assignee: Sergio Peña
>
> In HadoopThriftAuthBridge20S methods createClientWithConf and getCurrentUGIWithConf we create new Configuration objects so we can set the authentication type. When loading the new Configuration object, it looks like core-site.xml for the cluster it's connected to.
> This causes issues for Oozie since oozie does not have access to the core-site.xml as it's cluster agnostic.
--
This message was sent by Atlassian JIRA
(v6.2#6252)