Yes I did. Adding the hive proxy user settings to the service wide core-site.xml value under hdfs in cloudera manager and restarting hbase fixed it.
There is a setting in the GUI for the hive proxy users, but it was only set in the core-site.xml file that was distributed with the hdfs service, and was not included for any other service until I added it as an override in cloudera manager. Thanks for everyone's help and suggestions. I should have checked the core-site.xml file that was distributed with hbase. I saw the proxy user setting enabled in the core settings and assumed it was propagated to the other services. Justin Sent from my iPhone On Dec 15, 2013, at 3:18 AM, Lefty Leverenz <[email protected]> wrote: Justin, did you get any help with this? I can't give you pointers, sorry -- no expertise in this area. -- Lefty On Wed, Dec 11, 2013 at 7:10 AM, Justin Workman <[email protected]>wrote: > Yes, thanks for the reply. I found that one yesterday. I was trying to > patch 0.94 yesterday without success. Many unit tests failed during build. > > Any pointers? > > Sent from my iPhone > > On Dec 11, 2013, at 3:13 AM, Lefty Leverenz <[email protected]> > wrote: > > Did you see this JIRA? https://issues.apache.org/jira/browse/HBASE-8662 > > -- Lefty > > > On Mon, Dec 9, 2013 at 8:35 AM, Justin Workman > <[email protected]>wrote: > >> I have just started to experiment with Hbase in our cluster. I have an >> secure Hbase cluster setup and would like to create an external Hive table >> around several of our Hbase tables. This works fine until we enabled secure >> (kerberos) client access to Hbase. Now we cannot query any of our Hive >> external Hbase tables. >> >> Is there anyway to make this work, or plans to fix what appears to be an >> impersonation issue with Hbase? I wasn't able to find and specific Jira's. >> >> I am using CDH4.3.0 with the standard components that shipped with >> CDH4.3.0. >> >> Thanks >> Justin >> > >
