[ https://issues.apache.org/jira/browse/DRILL-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385335#comment-15385335 ]
Paul Rogers edited comment on DRILL-4791 at 7/20/16 6:02 AM: ------------------------------------------------------------- Absolutely. Nevertheless, please see the attached proposal for why a "light weight" and "versioned" API may be helpful for client apps. The proposal suggests a revised JDBC interface on top of the light-weight client. By light-weight, here I mean a new JDBC that is 1% the size of the current one, and does not depend on ZK. Plus, a new low-level protocol that is easy to implement in C, Python or anything that supports plain old sockets. was (Author: paul-rogers): Absolutely. Nevertheless, please see the attached proposal for why a "light weight" and "versioned" API may be helpful for client apps. The proposal suggests a revised JDBC interface on top of the light-weight client. > Provide a light-weight, versioned client API > -------------------------------------------- > > Key: DRILL-4791 > URL: https://issues.apache.org/jira/browse/DRILL-4791 > Project: Apache Drill > Issue Type: New Feature > Reporter: Paul Rogers > Assignee: Paul Rogers > > Drill's existing client APIs are "industrial strength" - they provide full > access to the sophisticated distributed, columnar RPCs which Drill uses > internall. However, they are too complex for most client needs. Provide a > simpler API optimized for clients: row-based result sets, synchronous, etc. > At the same time, Drill clients must currently link with the same version of > Drill code as is running on the Drill cluster. This forces clients to upgrade > in lock-step with the cluster. Allow Drill clients to be upgraded after (or > even before) the Drill cluster to simplify management of desktop apps that > use Drill. -- This message was sent by Atlassian JIRA (v6.3.4#6332)