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

(+dev@drill.apache.org bcc u...@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

Hi Laurent, That's right; this was mentioned in the design document. I am piggybacking on previous changes that break the "newer clients talking to older servers" compatibility. For example, as I understand, some resolved sub-tasks of DRILL-4714 [1] *implicitly* break this compatibility; say the

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

Just for clarity, DRILL-4280 is a breaking-protocol change, so is the plan to defer this change to a later release, or to defer bringing back compatibility between newer clients and older servers to a later release? Laurent On Tue, Nov 1, 2016 at 3:43 PM, Zelaine Fong wrote:

Apache Drill Hangout Minutes - 11/1/16

Attendees: Paul, Padma, Sorabh, Boaz, Sudheesh, Vitalii, Roman, Dave O, Arina, Laurent, Kunal, Zelaine I had to leave the hangout at 10:30, so my notes only cover the discussion up till then. 1) Variable width decimal support - Dave O Currently Drill only supports fixed width byte array storage