Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9717E103F6 for ; Tue, 25 Mar 2014 16:32:29 +0000 (UTC) Received: (qmail 74886 invoked by uid 500); 25 Mar 2014 16:32:25 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 74756 invoked by uid 500); 25 Mar 2014 16:32:22 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 74014 invoked by uid 500); 25 Mar 2014 16:32:18 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 73691 invoked by uid 99); 25 Mar 2014 16:32:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Mar 2014 16:32:18 +0000 Date: Tue, 25 Mar 2014 16:32:17 +0000 (UTC) From: "Prasad Mujumdar (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-6741) HiveServer2 startup fails in secure (kerberos) mode due to backward incompatible hadoop change MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946756#comment-13946756 ] Prasad Mujumdar commented on HIVE-6741: --------------------------------------- [~vaibhavgumashta] Thanks for looking into the problem. [HADOOP-10211|https://issues.apache.org/jira/browse/HADOOP-10211] seems to be fixed in Hadoop 2.4 and trunk (3.0), which are both unreleased hadoop versions. Hive is still using last hadoop release 2.3.0. Shouldn't this wait till we upgrade hadoop dependencies ? > HiveServer2 startup fails in secure (kerberos) mode due to backward incompatible hadoop change > ---------------------------------------------------------------------------------------------- > > Key: HIVE-6741 > URL: https://issues.apache.org/jira/browse/HIVE-6741 > Project: Hive > Issue Type: Bug > Components: HiveServer2 > Affects Versions: 0.13.0 > Reporter: Vaibhav Gumashta > Assignee: Vaibhav Gumashta > Priority: Blocker > Fix For: 0.13.0 > > Attachments: HIVE-6741.1.patch > > > [HADOOP-10211|https://issues.apache.org/jira/browse/HADOOP-10211] made a backward incompatible change due to which the following hive call returns a null map ([HiveAuthFactory-old|https://github.com/apache/hive/blob/fc3fdb19668369c56994d11df3207e14f2c5dba8/service/src/java/org/apache/hive/service/auth/HiveAuthFactory.java#L115]): > {code} > Map hadoopSaslProps = ShimLoader.getHadoopThriftAuthBridge(). > getHadoopSaslProperties(conf); > SaslQOP hadoopSaslQOP = SaslQOP.fromString(hadoopSaslProps.get(Sasl.QOP)); > if(hadoopSaslQOP.ordinal() > saslQOP.ordinal()) { > LOG.warn(MessageFormat.format("\"hadoop.rpc.protection\" is set to higher security level " + > "{0} then {1} which is set to {2}", hadoopSaslQOP.toString(), > ConfVars.HIVE_SERVER2_THRIFT_SASL_QOP.varname, saslQOP.toString())); > } > {code} > Since this code path is only used for logging hadoop sasl qop values in case hadoop's qop > hive's qop, we can do away with this and add a general log message. -- This message was sent by Atlassian JIRA (v6.2#6252)