03-18-2015 11:02 PM
All the documentation I find states that I should use
beeline> !connect jdbc:hive2://localhost:21050/;auth=noSasl
to connect to impala. Which it does.
Still the behavior seems to be very different if I want to connect with
$ beeline -u connect jdbc:hive2://localhost:21050/;auth=noSasl
Connecting to jdbc:hive2://node01.intranet.net:21050/ <----- missing the authentication config!!!
The problem is that I'm trying to connect to impala through hive2 action on Oozie, which will use the command line parameter and therefore simply hang all workflows.
Is this a bug of beeline ? If not, what can I use to state the authentication mechanism I need ?
03-21-2015 04:45 AM
From the command line it is working fine and it did the trick.
Using the hive2 action though, although the connection string is used, the action also injects a -a delegationToken in the command line. In the source I see:
+ // This tells BeeLine to look for a delegation token; otherwise it won't and will fail in secure mode because there are no + // Kerberos credentials. In non-secure mode, this argument is ignored so we can simply always pass it. + arguments.add("-a"); + arguments.add("delegationToken");
What I see is that the argument "is not ignored" even if I have the auth=noSasl in the driver definition.... Any other ideas ?
03-24-2015 12:12 PM
I'm not very familiar with the HS2 Oozie action. I'd suggest you try asking your question on email@example.com. Someone more knowledgable on this topic might be able to help.