So I am following https://drill.apache.org/docs/configuring-user-authentication/
And getting Authentication setup The suggested sqlline –u jdbc:drill:zk=10.10.11.112:5181 –n bob –p bobdrill Works great. (Obviously I use my ZK, my username, and my password) So being a sql guy, I now have some concerns that I couldn't find answers too, so I thought I'd toss them out here 1. If I specify the wrong password, I get more than a page of exception messages (Handshake validation, AUth Failed) etc. With full stack traces. Isn't this something that should be captured and minimized to a user? When I first set this up, it is difficult to determine what is related to issues with my auth setup and what is just a bad user/pass. I would argue from a pure programming point of view, and bad set of credentials is a normal occurrence, not an exception, yet the busy stack trace does not help me understand if things are setup, or if I just fatfingered my password. 2. I found no way with SQLLINE to authenticate without specifying my password at the command line if I did -n bob with no -p, there was a large exception (TL;DR Auth failed) if I did -n bob -p (with nothing else, hoping from a prompt) I got an array Index out of bounds If I did -n bob -p - (Hoping for a STDIN prompt) I got the large exception auth failed. I guess, I don't want my password in my .bash_history, and that shouldn't be a challenge. Hive does this, mysql, etc all do this. Is there a way to do this with Drill/SQL line? Thanks John
