Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
0.14.0
-
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
Attachments
Issue Links
- blocks
-
HIVE-6960 Set Hive pom to use Hadoop-2.4
- Closed
- is duplicated by
-
HIVE-8154 HadoopThriftAuthBridge20S.getHadoopSaslProperties is incompatible with Hadoop 2.4.1 and later
- Closed
- is related to
-
HIVE-7620 Hive metastore fails to start in secure mode due to "java.lang.NoSuchFieldError: SASL_PROPS" error
- Closed
-
HADOOP-10451 Remove unused field and imports from SaslRpcServer
- Closed
- relates to
-
HIVE-6987 Metastore qop settings won't work with Hadoop-2.4
- Closed