Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 645DC200B6F for ; Wed, 20 Jul 2016 08:03:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 63601160A8B; Wed, 20 Jul 2016 06:03:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B540E160A76 for ; Wed, 20 Jul 2016 08:03:21 +0200 (CEST) Received: (qmail 32048 invoked by uid 500); 20 Jul 2016 06:03:20 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 31994 invoked by uid 99); 20 Jul 2016 06:03:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jul 2016 06:03:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 73F172C0031 for ; Wed, 20 Jul 2016 06:03:20 +0000 (UTC) Date: Wed, 20 Jul 2016 06:03:20 +0000 (UTC) From: "Paul Rogers (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (DRILL-4791) Provide a light-weight, versioned client API MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 20 Jul 2016 06:03:22 -0000 [ 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)