They are different although interestingly I think some of this has been fixed per what others here have posted. If it were me I'd clarify/enhance the JIRA based on what you've just learned but others may feel differently.
Keys _______________________________ Keys Botzum Senior Principal Technologist [email protected] <mailto:[email protected]> 443-718-0098 MapR Technologies http://www.mapr.com <http://www.mapr.com/> > On Feb 3, 2016, at 5:20 PM, John Omernik <[email protected]> wrote: > > LOL So I did. > > I saw them as two things. "Not putting the password at the command line" > vs. Specifying the Connect string URL without user or pass and then getting > prompted... but in reality they really are the same thing aren't they? > > > > On Wed, Feb 3, 2016 at 4:18 PM, Keys Botzum <[email protected] > <mailto:[email protected]>> wrote: > >> Did you already open a JIRA on this? >> >> https://issues.apache.org/jira/browse/DRILL-3880 >> <https://issues.apache.org/jira/browse/DRILL-3880> >> >> >> Keys >> _______________________________ >> Keys Botzum >> Senior Principal Technologist >> [email protected] <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>> >> 443-718-0098 >> MapR Technologies >> http://www.mapr.com <http://www.mapr.com/> <http://www.mapr.com/ >> <http://www.mapr.com/>> >>> On Feb 3, 2016, at 5:14 PM, John Omernik <[email protected]> wrote: >>> >>> Ya, Andries, that's effectively what I did with my script, I passed the >> url >>> with -u, but without the username and password provided on the command >>> line, I get an auth error. If there truly is no way to ask for >>> username/password when providing auth string, I may open a JIRA on that, >> I >>> think it would be a helpful feature. Right now my work around is to use >> the >>> bash script to echo out what they need to type to get into drill :) >>> >>> >>> >>> On Wed, Feb 3, 2016 at 4:03 PM, Christopher Matta <[email protected]> >> wrote: >>> >>>> The only way I know of getting sqlline to ask for a password is to run >> the >>>> !connect command after starting the shell: >>>> >>>> $ /opt/mapr/drill/drill-1.4.0/bin/sqlline >>>> apache drill 1.4.0 >>>> "a drill in the hand is better than two in the bush" >>>> sqlline> !connect jdbc:drill: >>>> scan complete in 427ms >>>> Enter username for jdbc:drill:: cmatta >>>> Enter password for jdbc:drill:: ************** >>>> >>>> I’m not sure how to send that string to the sqlline shell once it’s >> opened >>>> though.. >>>> >>>> >>>> Chris Matta >>>> [email protected] >>>> 215-701-3146 >>>> >>>> On Wed, Feb 3, 2016 at 4:53 PM, John Omernik <[email protected]> wrote: >>>> >>>>> Hey all, I am trying to "Ease" my users into using drill. >>>>> >>>>> One thing that I'd like to automate for them is the initial connection, >>>>> basically, my zk string >>>>> >>>>> jdbc:drill:zk:zknode1:5181,zknode2:5181,zknode3:5181 >>>>> >>>>> Is a bit of pain, in addition, my users have to find sqlline, so what >> if >>>> I >>>>> change versions etc... my idea was to put an executable script in >>>> /usr/sbin >>>>> named zetadrill (zeta is a nod To Mr. Scott!) >>>>> >>>>> Basically, that has the path and I hoped the connect string so users >>>> would >>>>> not have to find my sqlline, nor would they have to know/remember >>>> zookeeper >>>>> information. Ideal world: They'd type zetadrill and it would say >> "Please >>>>> enter Username" "Please enter password" and they'd be good to go. >>>>> >>>>> So I tried using -u flag. >>>>> >>>>> When I do that (without a username and password) it fails out on me, >>>>> basically telling me that auth failed (invalid user credentials). >>>>> >>>>> I obviously can't put a username and password in the script, running >> the >>>>> connect with -u and -n (no password) results in the same failure. >>>>> >>>>> I guess I am asking: Is there any way to provide a connection string, >> and >>>>> then have sqlline prompt for credentials? This would make the user exp >> so >>>>> much better. >>>>> >>>>> Thanks in advanced!
