Vaibhav Gumashta created HIVE-6741:
--------------------------------------

             Summary: 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


 [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<String, String> 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)

Reply via email to