Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-6741

HiveServer2 startup fails in secure (kerberos) mode due to backward incompatible hadoop change

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 0.14.0
    • Fix Version/s: 0.14.0
    • Component/s: HiveServer2
    • Labels:
      None

      Description

      HADOOP-10211 made a backward incompatible change due to which the following hive call returns a null map (HiveAuthFactory-old):

      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()));
      }
      

      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.

        Attachments

        1. HIVE-6741.3.patch
          4 kB
          Vaibhav Gumashta
        2. HIVE-6741.2.patch
          2 kB
          Vaibhav Gumashta
        3. HIVE-6741.1.patch
          2 kB
          Vaibhav Gumashta

          Issue Links

            Activity

              People

              • Assignee:
                vgumashta Vaibhav Gumashta
                Reporter:
                vgumashta Vaibhav Gumashta
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: