Created on 12-19-2015 08:24 PM - edited 08-19-2019 05:29 AM
Hi ,
I upgraded Ambari from 2.0.1 to 2.1.2 and while investigating into a beeline issue I detected a possible 'mis-behaviour' in the Hive config section
Why are the properties 'hive.security.authorization.manager' and 'hive.security.authorization.enabled' listed twice ? And what me concerns even more, the auth.manager is listed with different values ?!?!?!
A check of the hiveserver2-site.xml shows the XaSecure... -setting seems to be applied
$ grep -E2 hive.security.authorization.manager hive*.xml hiveserver2-site.xml- </property> hiveserver2-site.xml- <property> hiveserver2-site.xml: <name>hive.security.authorization.manager</name> hiveserver2-site.xml- <value>com.xasecure.authorization.hive.authorizer.XaSecureHiveAuthorizerFactory</value> hiveserver2-site.xml- </property> -- hiveserver2-site.xml- <property> hiveserver2-site.xml- <name>hive.conf.restricted.list</name> hiveserver2-site.xml: <value>hive.security.authorization.enabled,hive.security.authorization.manager,hive.security.authenticator.manager</value> hiveserver2-site.xml- </property> hiveserver2-site.xml-</configuration>
Do I have a messed up config, or is this a bug in Ambari ?!?!
Created on 12-19-2015 11:43 PM - edited 08-19-2019 05:29 AM
This is from my env before enabling Ranger for Hive
This is after Ranger
I believe that it's normal
Created on 12-19-2015 11:43 PM - edited 08-19-2019 05:29 AM
This is from my env before enabling Ranger for Hive
This is after Ranger
I believe that it's normal
Created 12-20-2015 10:50 AM
Thanks @Neeraj Sabharwal
You are not concerned about having different values for "Enable authorization" before enabling Ranger 😉 ?