Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Community Articles

Find and share helpful community-sourced technical articles.
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!
Labels (1)
avatar

Description: Once you have a Hadoop cluster that is using Kerberos for authentication, you have to do the following in Ambari to configure Knox to work with that cluster.

1) Grant proxy privileges for Knox in core-site.xml

hadoop.proxyuser.knox.groups=*
hadoop.proxyuser.knox.hosts=*

2) Grant proxy privileges for Knox in webhcat-site.xml

webhcat.proxyuser.knox.groups=*
webhcat.proxyuser.knox.hosts=*

3) Grant proxy privileges for Knox in oozie-site.xml

oozie.service.ProxyUserService.proxyuser.knox.groups=*
oozie.service.ProxyUserService.proxyuser.knox.hosts=*

4) Update hive-site.xml and set the following properties on Hive Server2 hosts. Some of the properties may already be in the hive-site.xml. Ensure that the values match the ones below.

hive.server2.allow.user.substitution=true
hive.server2.transport.mode=http
hive.server2.thrift.http.port=10001
hive.server2.thrift.http.path=cliservice

NOTE: The properties shown above allows all users and all hostnames. Please consider security and update the value per your architecture.

For more info please visit this link

2,259 Views
0 Kudos
Version history
Last update:
‎11-27-2017 02:39 PM
Updated by:
Contributors