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 13054200D61 for ; Tue, 19 Dec 2017 16:53:39 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 11324160C1B; Tue, 19 Dec 2017 15:53:39 +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 7DE52160C18 for ; Tue, 19 Dec 2017 16:53:38 +0100 (CET) Received: (qmail 11904 invoked by uid 500); 19 Dec 2017 15:53:32 -0000 Mailing-List: contact dev-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list dev@flink.apache.org Received: (qmail 11893 invoked by uid 99); 19 Dec 2017 15:53:32 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Dec 2017 15:53:32 +0000 Received: from [192.168.178.63] (ip-2-205-80-95.web.vodafone.de [2.205.80.95]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id E97341A0112 for ; Tue, 19 Dec 2017 15:53:31 +0000 (UTC) To: dev@flink.apache.org From: Timo Walther Subject: [DISCUSS] FLIP-24 - SQL Client Message-ID: <8a9d718b-5dae-0fe2-1da6-a8d557d45582@apache.org> Date: Tue, 19 Dec 2017 16:53:29 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------3C303D05250C37876E173BD2" archived-at: Tue, 19 Dec 2017 15:53:39 -0000 --------------3C303D05250C37876E173BD2 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hey everyone, in the past, the community already asked about having a way to write Flink jobs without extensive programming skills. During the last year we have put a lot of effort in the core of our Table & SQL API. Now it is time to improve the tooling around it as well and make Flink more accessible. I already opened an issue for adding a SQL CLI client [0]. We developed a small protoype at data Artisans that was shown at the last Flink Forward Berlin [1]. For Flink 1.5 it would be great to offer at least a CLI client to play around with Flink and use it for debugging/demo purposes. We created a FLIP-24 [2] that roughly sketches the functionality and architecture. We also show how this architecture can evolve from a CLI client to a SQL gateway/REST server. Most of it is still up for dicussion. The targeted minimum viable product for Flink 1.5 should act as a start for collecting feedback and attracting contributors. So feedback on this FLIP is very welcome. What do you think? Regards, Timo [0] https://issues.apache.org/jira/browse/FLINK-7594 [1] https://berlin-2017.flink-forward.org/kb_sessions/from-streams-to-tables-and-back-again-a-demo-of-flinks-table-sql-api/ [2] https://cwiki.apache.org/confluence/display/FLINK/FLIP-24+-+SQL+Client --------------3C303D05250C37876E173BD2--