Re: Apache Drill Hangout Minutes - 11/1/16

(+d...@drill.apache.org bcc user@drill.apache.org) other options: - let the user decide between plain auth and sasl auth - let the client could send a flag to announce support for SASL auth, and do not send the credentials in the first handshake. An old server would then send AUTH_FAILED (and drop

Re: Apache Drill Hangout Minutes - 11/1/16

That's a good point that the introduction of new request types for prepared statement and metadata introduced some incompatibility issues, and that's why I added a client/server version exchange so that client can make smart decisions about using these new methods or not (this is the approach used

Re: Apache Drill Hangout Minutes - 11/1/16

I am going to update the pull request so that both will be "ok". This implies that username/password credentials will be sent to the server twice, during handshake and during SASL exchange. And sending credentials through handshake will be deprecated (and removed in a future release). Thank you,

Re: DRILL_LOG_PREFIX in drill-config

That works, sorry I was not able to suggest changes yesterday, I was heads down on a bunch of stuff, this would work for me. However, won't we have to change drill-config.sh so it doesn't hard code DRILL_LOG_PREFIX? John On Tue, Nov 1, 2016 at 1:14 PM, Paul Rogers wrote: