-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HBaseTap for secure HBase cluster #15
Comments
This pull request in cascading.hbase deals with a similar issue |
SpyGlass is not based on Cascading/HBaseTap, need to implement the fix here too |
Hi sathish316, I actually applied the same fix too. I'm currently testing it. Thank you for your contribution! |
Great! I've tested this patch on a hbase table with kerberos auth and reads are working fine. |
Just a question, do you need the fix for CDH 4.5.x? Because I'm applying the fix into the branch I'm working on to add support for CDH 5.1? I can try and release for both if you need it otherwise we were planning to move the master branch to CDH 5 |
I need the fix for CDH4.5 |
Ok, so I'll merge your one on the master branch and keep the other I'm testing to the CDH 5.1 branch. I would probably keep the two releases separate then. Another point. In my fix I added the following two lines to parallelai.spyglass.base.JobRunner: if (User.isHBaseSecurityEnabled(conf)) { Did you do that call in your client code? I can apply the same change also on the master branch so you can remove the code from the client code and simply use the JobRunner to launch the job |
I'm doing TokenUtil.obtainAndCacheToken in client code. |
Version 2.10_0.10_4.4 has been released on Conjars |
Does this work with secure HBase cluster?
In a HBase mapreduce job written in java, TableMapReduceUtil.initTableMapperJob internally calls TableMapReduceUtil.initCredentials. What is the equivalent of this in SpyGlass HBase taps for working with secure HBase?
If i don't do this step, it results in Kerberos errors in map step:
"No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)"
The text was updated successfully, but these errors were encountered: