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 704FE200D20 for ; Tue, 17 Oct 2017 13:33:39 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6EA181609EB; Tue, 17 Oct 2017 11:33: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 3D8C01609DE for ; Tue, 17 Oct 2017 13:33:38 +0200 (CEST) Received: (qmail 51861 invoked by uid 500); 17 Oct 2017 11:33:37 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 51849 invoked by uid 99); 17 Oct 2017 11:33:36 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Oct 2017 11:33:36 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E40A0CDC3A for ; Tue, 17 Oct 2017 11:33:35 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.98 X-Spam-Level: *** X-Spam-Status: No, score=3.98 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, KAM_BADIPHTTP=2, KAM_SHORT=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gridgain-com.20150623.gappssmtp.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id QpoGeBgY9B-H for ; Tue, 17 Oct 2017 11:33:32 +0000 (UTC) Received: from mail-wm0-f51.google.com (mail-wm0-f51.google.com [74.125.82.51]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 585A261139 for ; Tue, 17 Oct 2017 11:33:31 +0000 (UTC) Received: by mail-wm0-f51.google.com with SMTP id q132so3286424wmd.2 for ; Tue, 17 Oct 2017 04:33:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gridgain-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=0Wqo9O0AEhrgkLfKLZMSYvDDD9DOf+q/9GQxUIkG8fs=; b=CAjUkncUYUA+l6EZLt/1Knk5sRyIXuUfkIRyyvGClwED2bXuydkw2o2wSwJjdKOIlu 7bB5iEOGLj8AwMDDs029+LEJ8ME5RXswHedxrR7ELDlZPNJyn+mUw3vCFJL6EZvFTCiK jf8Nthx92GGIRZBBAgo8eS43DH1Rsxu4JVaarmpDWxYvO996Wst5ZKJ+my6syGc9i9kW 6H4mRCTsPISx3hdrBq9VBzw4l2HjfDi6YfhEWY6/K8gJyD5qoBl7Bisp/ocpPUbLKADB C6PgCb4r56Rl6YV5g3YYg78K7hPzEY7/oMS3g+63sozXLzZ3YCoa0ZYh+RSwWmZVOr8k O2cA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=0Wqo9O0AEhrgkLfKLZMSYvDDD9DOf+q/9GQxUIkG8fs=; b=cUnGV1g491S4CZ03NxgecZo+ZZHKNT/RC2nxl6A6yPHAyFVNpwnUfZOKn9u3xjQwkP se68e+ClZGh6/950RoRMyh3N1iXaU6sgp1vFSjMtr8NFYSvsk8SyKrPvCTEBf9BqBqiq qYDdIK2hPQVAScYwawz4vUUwDS5O6zgiHjYIi15D7Fgcpl2ny0NlKPZitlKS0yoVWJNQ u/qocOsXs1AdHwig43NNiXrs3B6pWI7+5861kXEEIcKMnjLJIsDRuhb6TMrpp4iTWSFP Vy22PLYQUpWR4RbajQoji43tHhM7aR2E7feA5XXbOLvj36YukCcjWlw/eUB333cHJNwd LzSw== X-Gm-Message-State: AMCzsaXN+JvdsEYb1Z/dOPsUjD2PBgkhMLgFYnD95ifEENx0fEcUFTTA VWa/OUc7GGxVfl3TyspuQo6UsrpqJxmCAHBVI0Xg6EFo X-Google-Smtp-Source: AOwi7QDFfxwVYyASYUON+hyPYKrEAYvwxfMRp5oepihtIJQ32m/gSOAQP+QEaccTW1hOF2M3z5g8jh7xsPsYDYIDkXI= X-Received: by 10.80.230.140 with SMTP id z12mr16461967edm.28.1508240009785; Tue, 17 Oct 2017 04:33:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.245.164 with HTTP; Tue, 17 Oct 2017 04:33:29 -0700 (PDT) In-Reply-To: <2094EBF7-236C-446F-A595-122D164F1B68@apache.org> References: <19BBC834-B22D-4CBF-B6B4-8A1405227959@apache.org> <0CAB33E3-1E6C-48A2-9131-7D9BE3E1FDAB@apache.org> <3ad7522f-60df-4ea6-bafd-c0e336ad702b@apache.org> <8C8201C8-3815-4183-A499-7EBD9ED2B408@apache.org> <2094EBF7-236C-446F-A595-122D164F1B68@apache.org> From: Oleg Ostanin Date: Tue, 17 Oct 2017 14:33:29 +0300 Message-ID: Subject: Re: Adding sqlline tool to Apache Ignite project To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="089e082f7e8c050b01055bbc7ed2" archived-at: Tue, 17 Oct 2017 11:33:39 -0000 --089e082f7e8c050b01055bbc7ed2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable New example build with sqlline: https://ci.ignite.apache.org/viewLog.html?buildId=3D894407&tab=3Dartifacts&= buildTypeId=3DIgniteRelease_XxxFromMirrorIgniteRelease3PrepareVote#!1rrb2,1= esn4zrslm4po,-h8h0hn9vvvxp On Wed, Oct 11, 2017 at 1:00 AM, Denis Magda wrote: > Oleg, > > Looks good to me. Please consider the notes left in the ticket. I want us > to prepare a script for Windows, review the language for help notice and > errors, put together documentation. Prachi will be able to help with the > editing and documentation. > > =E2=80=94 > Denis > > > On Oct 9, 2017, at 10:13 AM, Oleg Ostanin wrote= : > > > > New build with fixed argument parsing: > > https://ci.ignite.apache.org/viewLog.html?buildId=3D882282& > tab=3Dartifacts&buildTypeId=3DIgniteRelease_XxxFromMirrorIgniteRelease3Pr= e > pareVote#!1rrb2,1esn4zrslm4po,-h8h0hn9vvvxp > > > > On Mon, Oct 9, 2017 at 5:38 PM, Denis Magda wrote= : > > > >> I think it=E2=80=99s a must have for the ticket resolution. > >> > >> Denis > >> > >> On Monday, October 9, 2017, Anton Vinogradov > >> wrote: > >> > >>> Any plans to have ignitesql.bat? > >>> > >>> On Mon, Oct 9, 2017 at 5:29 PM, Oleg Ostanin >>> > wrote: > >>> > >>>> Another build with sqlline included: > >>>> https://ci.ignite.apache.org/viewLog.html?buildId=3D881120& > >>>> tab=3Dartifacts&buildTypeId=3DIgniteRelease_ > XxxFromMirrorIgniteRelease3Pre > >>>> pareVote#!1rrb2,-wpvx2aopzexz,1esn4zrslm4po,-h8h0hn9vvvxp > >>>> > >>>> On Sun, Oct 8, 2017 at 5:11 PM, Denis Magda >>> > wrote: > >>>> > >>>>> No more doubts on my side. +1 for Vladimir=E2=80=99s suggestion. > >>>>> > >>>>> Denis > >>>>> > >>>>> On Saturday, October 7, 2017, Dmitriy Setrakyan < > >> dsetrakyan@apache.org > >>> > > >>>>> wrote: > >>>>> > >>>>>> I now tend to agree with Vladimir. We should always require that > >> some > >>>>>> address is specified. The help menu should clearly state how to > >>> connect > >>>>> to > >>>>>> a localhost. > >>>>>> > >>>>>> D. > >>>>>> > >>>>>> On Sat, Oct 7, 2017 at 12:44 AM, Vladimir Ozerov < > >>> vozerov@gridgain.com > >>>>>> > > >>>>>> wrote: > >>>>>> > >>>>>>> Denis, > >>>>>>> > >>>>>>> Default Ignite configuration uses multicast, this is why you do > >> not > >>>>> need > >>>>>> to > >>>>>>> change anything. Ignite node is always both a server (listens) > >> and > >>> a > >>>>>> client > >>>>>>> (connects). > >>>>>>> > >>>>>>> This will not work for ignitesql, as this is a client. And in > >> real > >>>>>>> deployments it will connect to remote nodes, not local. So the > >>>> earlier > >>>>> we > >>>>>>> explain user how to do this, the better. This is why it should > >> not > >>>> work > >>>>>> out > >>>>>>> of the box connecting to 127.0.0.1. No magic for users please. > >>>>>>> > >>>>>>> This is what user will see (draft): > >>>>>>>> ./ignitesql.sh > >>>>>>>> Please specify the host: ignitesql.sh [host]; type --help for > >>> more > >>>>>>> information. > >>>>>>>> ./ignitesql.sh 192.168.12.55 > >>>>>>>> Connected successfully. > >>>>>>> > >>>>>>> Again, specifying parameters manually is not poor UX. This is > >>>> excellent > >>>>>> UX, > >>>>>>> as user learns on his own how to connect to a node in 1 minute. > >>> Most > >>>>>>> command line tools work this way. > >>>>>>> > >>>>>>> =D1=81=D0=B1, 7 =D0=BE=D0=BA=D1=82. 2017 =D0=B3. =D0=B2 7:12, Dmi= triy Setrakyan < > >>> dsetrakyan@apache.org > >>>>>> >: > >>>>>>> > >>>>>>>> How does the binding happen? Can we bind to everything, like we > >>> do > >>>> in > >>>>>>>> Ignite? > >>>>>>>> > >>>>>>>> On Fri, Oct 6, 2017 at 2:51 PM, Denis Magda >>> > >>>>>> > wrote: > >>>>>>>> > >>>>>>>>> Thought over 127.0.0.1 as a default host once again. The bad > >>>> thing > >>>>>>> about > >>>>>>>>> it is that the user gets a lengthy exception stack trace if > >>>> Ignite > >>>>>> is > >>>>>>>> not > >>>>>>>>> running locally and not a small error message. > >>>>>>>>> > >>>>>>>>> What are the other opinions on this? Do we want to follow > >>>>> Vladimir=E2=80=99s > >>>>>>>>> suggestion forcing to set the host name/IP (port is optional) > >>> for > >>>>> the > >>>>>>>> sake > >>>>>>>>> of usability or leaver 127.0.0.1 as default? > >>>>>>>>> > >>>>>>>>> =E2=80=94 > >>>>>>>>> Denis > >>>>>>>>> > >>>>>>>>>> On Oct 6, 2017, at 12:21 PM, Denis Magda < > >> dmagda@apache.org > >>> > >>>>>> > wrote: > >>>>>>>>>> > >>>>>>>>>>> But, we need to support =E2=80=9Chelp=E2=80=9D (-h, -help) ar= gument > >> listing > >>>> all > >>>>>> the > >>>>>>>>> parameters accepted by the tools. > >>>>>>>>>> > >>>>>>>>>> Meant accepted by the ignitesql script only such as host > >>> name. > >>>>>>>>>> > >>>>>>>>>> =E2=80=94 > >>>>>>>>>> Denis > >>>>>>>>>> > >>>>>>>>>>> On Oct 6, 2017, at 12:20 PM, Denis Magda < > >> dmagda@apache.org > >>> > >>>>>> > wrote: > >>>>>>>>>>> > >>>>>>>>>>> Really nice, could click through the getting started [1] > >> in > >>> a > >>>>>>> minute! > >>>>>>>>>>> > >>>>>>>>>>> +1 to rename the script to =E2=80=9Cignitesql=E2=80=9D. Vladi= mir=E2=80=99s point > >>> makes > >>>>>> total > >>>>>>>>> sense. > >>>>>>>>>>> > >>>>>>>>>>> However, tend to disagree that the host has to be > >> requested > >>>> all > >>>>>> the > >>>>>>>>> times. We never request a configuration or host name for > >>>> ignite.sh, > >>>>>>> visor > >>>>>>>>> or web agent scripts. I would follow this approach that=E2=80= =99s > >>>> excellent > >>>>>> for > >>>>>>>> dev > >>>>>>>>> time. > >>>>>>>>>>> > >>>>>>>>>>> But, we need to support =E2=80=9Chelp=E2=80=9D (-h, -help) ar= gument > >> listing > >>>> all > >>>>>> the > >>>>>>>>> parameters accepted by the tools. > >>>>>>>>>>> > >>>>>>>>>>> Please consider our feedback and share the next build once > >>>> it=E2=80=99s > >>>>>>> ready. > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> [1] https://apacheignite-sql.readme.io/v2.1/docs/getting- > >>>>> started > >>>>>> < > >>>>>>>>> https://apacheignite-sql.readme.io/v2.1/docs/getting-started > >>> > >>>>>>>>>>> > >>>>>>>>>>> =E2=80=94 > >>>>>>>>>>> Denis > >>>>>>>>>>> > >>>>>>>>>>>> On Oct 6, 2017, at 9:04 AM, Anton Vinogradov < > >>>>>>>> avinogradov@gridgain.com > > >>>>>>>>> wrote: > >>>>>>>>>>>> > >>>>>>>>>>>> How about sqlconsole.sh or sqlcmd.sh ? > >>>>>>>>>>>> > >>>>>>>>>>>> On Fri, Oct 6, 2017 at 6:04 PM, >>> > >>>>>> > wrote: > >>>>>>>>>>>> > >>>>>>>>>>>>> I like ignitesql. > >>>>>>>>>>>>> > >>>>>>>>>>>>> =E2=81=A3D.=E2=80=8B > >>>>>>>>>>>>> > >>>>>>>>>>>>> On Oct 6, 2017, 4:49 PM, at 4:49 PM, Vladimir Ozerov < > >>>>>>>>> vozerov@gridgain.com > > >>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>> Denis, > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Setting default host to 127.0.0.1 is bad idea, because > >> it > >>>>> mean > >>>>>>> that > >>>>>>>>> in > >>>>>>>>>>>>>> practice users would have to change the script always. > >>>>> Instead, > >>>>>>> we > >>>>>>>>>>>>>> should > >>>>>>>>>>>>>> accept host name as argument. This is perfectly fine > >> from > >>>>>>> usability > >>>>>>>>>>>>>> perspective, most tools work this way (i.e. throw error > >>>> when > >>>>>>>> started > >>>>>>>>>>>>>> without arguments). > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Also IMO "ignitedb" is misleading name. Users would > >> like > >>>>> think > >>>>>>> that > >>>>>>>>> it > >>>>>>>>>>>>>> is a > >>>>>>>>>>>>>> kind of script to start database, rather than to > >> connect > >>> to > >>>>> it. > >>>>>>> We > >>>>>>>>>>>>>> should > >>>>>>>>>>>>>> think on other names. E.g. "ignitesql". > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> On Fri, Oct 6, 2017 at 5:23 PM, Sergey Kozlov < > >>>>>>>> skozlov@gridgain.com > > >>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> Denis > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> The link below has included sqlline. Please take a > >> look: > >>>>>>>>>>>>>>> https://ci.ignite.apache.org/ > >>> viewLog.html?buildId=3D875441& > >>>>>>>>>>>>>>> buildTypeId=3DIgniteRelease_ > >>> XxxFromMirrorIgniteRelease3Pre > >>>>>>>>>>>>>>> pareVote&tab=3Dartifacts#!1rrb2,-wpvx2aopzexz > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> On Thu, Oct 5, 2017 at 7:48 PM, Denis Magda < > >>>>>> dmagda@apache.org > > >>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> Here is the original ticket [1]. Ilya, closed the one > >>>>> created > >>>>>>> by > >>>>>>>>>>>>>> you as a > >>>>>>>>>>>>>>>> duplicate. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> In addition to the tool=E2=80=99s jar inclusion in Ignit= e=E2=80=99s > >>>> binary > >>>>>>>> releases > >>>>>>>>>>>>>> let=E2=80=99s > >>>>>>>>>>>>>>>> create a shell script to simplify the connectivity > >>> phase: > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> - name the script as ignitedb.sh for Unix and > >>>> ignitedb.bat > >>>>>> for > >>>>>>>>>>>>>>> Windows. > >>>>>>>>>>>>>>>> - > >>>>>>>>>>>>>>>> - the script uses the following connection string by > >>>>> default: > >>>>>>>>>>>>>> .sqlline > >>>>>>>>>>>>>>>> -d org.apache.ignite.IgniteJdbcThinDriver > >> --color=3Dtrue > >>>>>>>>>>>>>> --verbose=3Dtrue > >>>>>>>>>>>>>>>> --showWarnings=3Dtrue --showNestedErrs=3Dtrue -u > >>> jdbc:ignite: > >>>>>>>>>>>>>>>> thin://127.0.0.1/ > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> - make up parameters list to adjust Ignite specific > >>> part > >>>> of > >>>>>> the > >>>>>>>>>>>>>>>> connection string: Ignite IP and port, streaming > >> mode, > >>>> etc. > >>>>>> The > >>>>>>>>>>>>>> full > >>>>>>>>>>>>>>> list > >>>>>>>>>>>>>>>> of supported parameters is here: > >> https://apacheignite- > >>>>>>>>>>>>>>>> sql.readme.io/docs/jdbc-driver#jdbc-thin-driver > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>> >>>>>>>>> jdbc-thin-driver > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> [1] https://issues.apache.org/ > >> jira/browse/IGNITE-5608 > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> =E2=80=94 > >>>>>>>>>>>>>>>> Denis > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> On Oct 5, 2017, at 9:02 AM, Sergey Kozlov < > >>>>>>> skozlov@gridgain.com > > >>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> Dmitriy, Denis > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> We're in progress to add sqlline in upcoming 2.3 > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> On Thu, Oct 5, 2017 at 5:30 PM, Dmitriy Setrakyan > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>> Would be nice to get it in 2.3. This is critical > >>>>>> functionality > >>>>>>>> for > >>>>>>>>>>>>>> our > >>>>>>>>>>>>>>>> users and 2.4 seems too far to give anyone comfort. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> On Thu, Oct 5, 2017 at 11:33 AM, Ilya Suntsov > >>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> Guys, > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> I've created the ticket for 2.4 release: > >>>>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-6561 > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> 2017-08-30 22:21 GMT+03:00 Julian Hyde < > >>>> jhyde@apache.org > >>>>>> >: > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> Denis, > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> I=E2=80=99m glad you=E2=80=99re thinking of using SQLL= ine. Under > >> the > >>>> BSD > >>>>>>>>>>>>>> license, you > >>>>>>>>>>>>>>>>>> don=E2=80=99t need my permission to distribute, but I = grant > >>>> that > >>>>>>>>>>>>>> permission. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> Drill, Phoenix and Calcite already distribute > >>> SQLLine, > >>>> so > >>>>>>>>>>>>>> Ignite is > >>>>>>>>>>>>>>> in > >>>>>>>>>>>>>>>>>> good company. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> If you need extensions, please discuss on the dev > >>> list, > >>>>> or > >>>>>>> open > >>>>>>>>>>>>>> a > >>>>>>>>>>>>>>>> GitHub > >>>>>>>>>>>>>>>>>> case or pull request. SQLLine operates in the usual > >>> way > >>>>>> for a > >>>>>>>>>>>>>> GitHub > >>>>>>>>>>>>>>>>>> project. It=E2=80=99s unlikely that you=E2=80=99ll nee= d > >>> Ignite-specific > >>>>>>>>>>>>>> extensions =E2=80=94 > >>>>>>>>>>>>>>>>>> SQLLine just exposes what comes through the JDBC > >>>> driver =E2=80=94 > >>>>>> but > >>>>>>>>>>>>>> we can > >>>>>>>>>>>>>>>>>> discuss if the need arises. The Hive project forked > >>>>> SQLLine > >>>>>>>>>>>>>> into its > >>>>>>>>>>>>>>>> own > >>>>>>>>>>>>>>>>>> Beeline module and I=E2=80=99d like to avoid a repeat = of > >>> that. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> Julian > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> On Aug 29, 2017, at 6:35 PM, Denis Magda < > >>>>>> dmagda@apache.org > >>>>>>>> > >>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> Igniters, > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> Let me introduce Julian Hyde [1], creator of > >> SQLLine > >>>>> tool > >>>>>>> and > >>>>>>>>>>>>>> our > >>>>>>>>>>>>>>>>> Apache > >>>>>>>>>>>>>>>>>> mate, > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> Julian, > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> Please grant that Apache Ignite community a > >>> permission > >>>>> to > >>>>>>>>>>>>>> include > >>>>>>>>>>>>>>>>>> SQLLine [2] it in every Ignite deliverable (source, > >>>>>> binary). > >>>>>>>>>>>>>> It=E2=80=99s > >>>>>>>>>>>>>>>> planned > >>>>>>>>>>>>>>>>>> to suggest the tool as a default command line SQL > >>>> utility > >>>>>> for > >>>>>>>>>>>>>> Ignite > >>>>>>>>>>>>>>>>>> clusters. SQLLite and Ignite usage will also be > >>>>> documented > >>>>>> on > >>>>>>>>>>>>>>> Ignite=E2=80=99s > >>>>>>>>>>>>>>>>>> technical documentation. > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> [1] https://people.apache.org/~jhyde/ < > >>>>>>>>>>>>>>> https://people.apache.org/~jh > >>>>>>>>>>>>>>>>> yde/ > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> [2] https://github.com/julianhyde/sqlline > >>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> julianhyde/sqlline> > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> =E2=80=94 > >>>>>>>>>>>>>>>>>>> Denis > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> On Aug 25, 2017, at 9:17 AM, Denis Magda < > >>>>>>> dmagda@apache.org > >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> dmagda@apache.org >> > >>> wrote: > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> Hi Ilya, > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> Thanks for the clarification! Referring to the > >> page > >>>>>> shared > >>>>>>>>>>>>>> by you > >>>>>>>>>>>>>>>> [1] > >>>>>>>>>>>>>>>>>> if we need to get author=E2=80=99s consent in a writte= n > >> form: > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> A permissive license similar to the BSD 2-Clause > >>>>> License, > >>>>>>>>>>>>>> but > >>>>>>>>>>>>>>> with a > >>>>>>>>>>>>>>>>>> 3rd clause that prohibits others from using the > >> name > >>> of > >>>>> the > >>>>>>>>>>>>>> project > >>>>>>>>>>>>>>> or > >>>>>>>>>>>>>>>>> its > >>>>>>>>>>>>>>>>>> contributors to promote derived products without > >>>> written > >>>>>>>>>>>>>> consent. > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> [1] > >>>>>>>>>>>>>> https://github.com/julianhyde/ > >>> sqlline/blob/master/LICENSE > >>>> < > >>>>>>>>>>>>>>>>>> https://github.com/julianhyde/ > >>>>> sqlline/blob/master/LICENSE> > >>>>>> < > >>>>>>>>>>>>>>>>>> https://github.com/julianhyde/ > >>>>> sqlline/blob/master/LICENSE > >>>>>> < > >>>>>>>>>>>>>>>>>> https://github.com/julianhyde/ > >>>>> sqlline/blob/master/LICENSE > >>>>>>>> > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> I=E2=80=99ll reach out the author requesting the per= mit. > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> =E2=80=94 > >>>>>>>>>>>>>>>>>>>> Denis > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> On Aug 25, 2017, at 9:12 AM, Ilya Kasnacheev < > >>>>>>>>>>>>>>>>>> ilya.kasnacheev@gmail.com > >>> >>>>>> ilya.kasnacheev@gmail.com > >>>>>>>>> > >>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> Hi Denis, > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> There are two kinds of BSD license, 3-clause and > >>>>>> 4-clause. > >>>>>>>>>>>>>> The > >>>>>>>>>>>>>>>>>> difference > >>>>>>>>>>>>>>>>>>>>> between them is advertising clause: > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> "3. All advertising materials mentioning > >> features > >>> or > >>>>> use > >>>>>>> of > >>>>>>>>>>>>>> this > >>>>>>>>>>>>>>>>>> software > >>>>>>>>>>>>>>>>>>>>> must display the following acknowledgement: This > >>>>> product > >>>>>>>>>>>>>> includes > >>>>>>>>>>>>>>>>>> software > >>>>>>>>>>>>>>>>>>>>> developed by the University of California, > >>> Berkeley > >>>>> and > >>>>>>> its > >>>>>>>>>>>>>>>>>> contributors." > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> which is causing problems with other licenses > >> and > >>>>> which > >>>>>>>>>>>>>> sqlline's > >>>>>>>>>>>>>>>>>> license > >>>>>>>>>>>>>>>>>>>>> doesn't contain: > >>>>>>>>>>>>>>>>>>>>> https://github.com/julianhyde/ > >>>>>> sqlline/blob/master/LICENSE > >>>>>>> < > >>>>>>>>>>>>>>>>>> https://github.com/julianhyde/ > >>>>> sqlline/blob/master/LICENSE> > >>>>>>>>>>>>>>>>>>>>> So it should be all good for inclusion. > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> -- > >>>>>>>>>>>>>>>>>>>>> Ilya Kasnacheev. > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> 2017-08-25 18:48 GMT+03:00 Denis Magda < > >>>>>> dmagda@apache.org > >>>>>>>> : > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> Hi Ilya, > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> It will be a useful addition to Ignite. I would > >>>>> include > >>>>>>>>>>>>>> the tool > >>>>>>>>>>>>>>>> in > >>>>>>>>>>>>>>>>>> one of > >>>>>>>>>>>>>>>>>>>>>> the nearest releases. It=E2=80=99s license is BSD-= 3 > >> which > >>>> is > >>>>>>>>>>>>>> compatible > >>>>>>>>>>>>>>>> with > >>>>>>>>>>>>>>>>>> ours. > >>>>>>>>>>>>>>>>>>>>>> However, there is a note on ASF side saying > >> that > >>>> BSD > >>>>>>>>>>>>>> licenses > >>>>>>>>>>>>>>> can > >>>>>>>>>>>>>>>> be > >>>>>>>>>>>>>>>>>>>>>> included without advertising clause [1]. What > >>> does > >>>> it > >>>>>>> mean > >>>>>>>>>>>>>> for > >>>>>>>>>>>>>>> us? > >>>>>>>>>>>>>>>>>> Can we > >>>>>>>>>>>>>>>>>>>>>> document the tool and mention on our site? > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> [1] https://www.apache.org/legal/ > >>>>>>> resolved.html#category-a > >>>>>>>>>>>>>> < > >>>>>>>>>>>>>>>>>>>>>> https://www.apache.org/legal/ > >>>>> resolved.html#category-a> > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> =E2=80=94 > >>>>>>>>>>>>>>>>>>>>>> Denis > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> On Aug 25, 2017, at 8:32 AM, Ilya Suntsov < > >>>>>>>>>>>>>>> isuntsov@gridgain.com > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> Hi Igniters, > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> I've found one command line tool that can be > >>> used > >>>>> for > >>>>>>>>>>>>>> execute > >>>>>>>>>>>>>>>>> queries > >>>>>>>>>>>>>>>>>>>>>>> (DDL/DML) with data from Apache Ignite grid > >> via > >>>>>>>>>>>>>>>>>>>>>>> *org.apache.ignite.IgniteJdbcThinDriver*. > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> Here you can find overview of internal > >> commands > >>> of > >>>>>> this > >>>>>>>>>>>>>> tool: > >>>>>>>>>>>>>>>>>>>>>>> https://cwiki.apache.org/ > >>>> confluence/display/IGNITE/ > >>>>>>>>>>>>>>>>>> Overview+sqlline+tool > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> The most problems with sqlline relate with > >> some > >>>>> issues > >>>>>>>>>>>>>> from our > >>>>>>>>>>>>>>>>> side > >>>>>>>>>>>>>>>>>> or > >>>>>>>>>>>>>>>>>>>>>>> some unsupported features. > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> Would be nice to add tool like this (sqlline > >> or > >>>>>>> something > >>>>>>>>>>>>>> else) > >>>>>>>>>>>>>>>> in > >>>>>>>>>>>>>>>>>> our > >>>>>>>>>>>>>>>>>>>>>>> project. > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> Have you any objections or other thoughts? > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> -- > >>>>>>>>>>>>>>>>>>>>>>> Ilya Suntsov > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> -- > >>>>>>>>>>>>>>>>> Ilya Suntsov > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> -- > >>>>>>>>>>>>>>>> Sergey Kozlov > >>>>>>>>>>>>>>>> GridGain Systems > >>>>>>>>>>>>>>>> www.gridgain.com > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> -- > >>>>>>>>>>>>>>> Sergey Kozlov > >>>>>>>>>>>>>>> GridGain Systems > >>>>>>>>>>>>>>> www.gridgain.com > >>>>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > > --089e082f7e8c050b01055bbc7ed2--