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 854A5200CEC for ; Mon, 21 Aug 2017 18:56:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8425B16564F; Mon, 21 Aug 2017 16:56:14 +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 C995F16564D for ; Mon, 21 Aug 2017 18:56:13 +0200 (CEST) Received: (qmail 94164 invoked by uid 500); 21 Aug 2017 16:56:12 -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 94153 invoked by uid 99); 21 Aug 2017 16:56:12 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Aug 2017 16:56:12 +0000 Received: from [192.168.75.66] (c-67-160-238-197.hsd1.ca.comcast.net [67.160.238.197]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id A2D991A002B for ; Mon, 21 Aug 2017 16:56:11 +0000 (UTC) From: Denis Magda Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: SQL usability issues Date: Mon, 21 Aug 2017 09:56:09 -0700 References: <4f57ea8d-1d42-7bce-f387-b19d5e83ce38@gridgain.com> To: dev@ignite.apache.org In-Reply-To: <4f57ea8d-1d42-7bce-f387-b19d5e83ce38@gridgain.com> Message-Id: <764D5D85-60F0-48EE-A3C5-6E9FAC03583D@apache.org> X-Mailer: Apple Mail (2.3273) archived-at: Mon, 21 Aug 2017 16:56:14 -0000 Thanks Taras, fixed the doc. Not sure how it worked before with the = wrong name. =E2=80=94 Denis > On Aug 21, 2017, at 5:05 AM, Taras Ledkov = wrote: >=20 > Hi, >=20 > Denis, please rename '|IgniteThinJdbcDriver| ' -> = 'IgniteJdbcThinDriver' an the Installation and Configuration section = (see [1]). >=20 > [1] = https://apacheignite.readme.io/docs/sql-tooling#installation-and-configura= tion >=20 >=20 > On 18.08.2017 0:22, Denis Magda wrote: >> No I see what you tried to convey. Here it is the doc: >> https://apacheignite.readme.io/docs/sql-tooling = >>=20 >> =E2=80=94 >> Denis >>=20 >>> On Aug 16, 2017, at 6:06 PM, Dmitriy Setrakyan = wrote: >>>=20 >>> Denis, >>>=20 >>> I agree with Val. I am OK with using DBeaver as an example, but the = name of >>> the doc should be generic and the doc should be updated stating that >>> DBeaver is just one example of how Ignite can be used with generic = SQL >>> viewer tools. >>>=20 >>> D. >>>=20 >>> On Wed, Aug 16, 2017 at 6:01 PM, Denis Magda = wrote: >>>=20 >>>> Val, >>>>=20 >>>> This article is generic: >>>> https://apacheignite.readme.io/docs/getting-started-sql < >>>> https://apacheignite.readme.io/docs/getting-started-sql> >>>>=20 >>>> DBeaver, Pentaho and Tableau are given as examples. >>>>=20 >>>> If the description or introduction of the tool should sound clearer = please >>>> suggest your version. >>>>=20 >>>> =E2=80=94 >>>> Denis >>>>=20 >>>>> On Aug 16, 2017, at 5:55 PM, Valentin Kulichenko < >>>> valentin.kulichenko@gmail.com> wrote: >>>>> Denis, >>>>>=20 >>>>> I think this article should be more generic, describing how to = connect a >>>>> generic JDBC tool to Ignite (probably using DBeaver as an = example). >>>>>=20 >>>>> Right now it looks like out of all such tools we support only = DBeaver for >>>>> some reason :) >>>>>=20 >>>>> What do you think? >>>>>=20 >>>>> -Val >>>>>=20 >>>>> On Wed, Aug 16, 2017 at 1:49 PM, Denis Magda = wrote: >>>>>=20 >>>>>> Igniters, >>>>>>=20 >>>>>> I=E2=80=99ve prepared the getting started basing on DBeaver tool: >>>>>> https://apacheignite-tools.readme.io/docs/dbeaver < >>>>>> https://apacheignite-tools.readme.io/docs/dbeaver> >>>>>>=20 >>>>>> That guide is based on the generic one made out by Akmal: >>>>>> https://apacheignite.readme.io/docs/getting-started-sql < >>>>>> https://apacheignite.readme.io/docs/getting-started-sql> >>>>>>=20 >>>>>> During the work on the guide we faced one more issue that = prevents us >>>> from >>>>>> using the bulk inserts: >>>>>> https://issues.apache.org/jira/browse/IGNITE-6092 < >>>>>> https://issues.apache.org/jira/browse/IGNITE-6092> >>>>>>=20 >>>>>> *Alexander P.*, *Vladimir*, how difficult is to support this = feature? >>>>>>=20 >>>>>> =E2=80=94 >>>>>> Denis >>>>>>=20 >>>>>>> On Aug 13, 2017, at 9:20 AM, Dmitriy Setrakyan = >>>>>> wrote: >>>>>>> On Fri, Aug 11, 2017 at 7:31 PM, Denis Magda = >>>>>> wrote: >>>>>>>> Dmitriy, >>>>>>>>=20 >>>>>>>> That's the documentation that shows how to configure Pentaho = via JDBC: >>>>>>>> https://apacheignite-tools.readme.io/v2.1/docs/pentaho >>>>>>>=20 >>>>>>> I am not sure I agree. Why would I look at Pentaho integration = when >>>>>> trying >>>>>>> to configure a generic SQL viewer tool? We need a generic = documentation >>>>>>> section for configuring JDBC/ODBC drivers with 3rd party tools. >>>>>>>=20 >>>>>>>=20 >>>>>>>>=20 >>>>>>>> Plus on the tools' domain you can see Tableau based ODBC = example. >>>>>>>>=20 >>>>>>>> So, I'm not sure we need something else from the documentation >>>>>> standpoint. >>>>>>>> I would rather add a direct reference from JDBC/ODBC docs to = Pentaho >>>> and >>>>>>>> Tablea. >>>>>>>>=20 >>>>>>>> Denis >>>>>>>>=20 >>>>>>>> On Friday, August 11, 2017, Dmitriy Setrakyan = >>>>>>>> wrote: >>>>>>>>=20 >>>>>>>>> Igniters, >>>>>>>>>=20 >>>>>>>>> I have tried to connect to Ignite from DBeaver [1], and = realized that >>>>>>>> there >>>>>>>>> are some usability issues we need to address before the next = release: >>>>>>>>>=20 >>>>>>>>> 1. We need to have documentation on how to configure JDBC and = ODBC >>>>>>>>> drivers with external SQL tools [2] >>>>>>>>> 2. You cannot highlight multiple SQL statements and run them >>>> together >>>>>>>>> [3] >>>>>>>>> 3. Commands like *DESCRIBE* or *SHOW* do not work [4] >>>>>>>>> 4. Schema, index, and table metadata is not displayed [5]. = Looks >>>> like >>>>>>>>> this fix was already implemented. >>>>>>>>>=20 >>>>>>>>> The links to the tickets are below. >>>>>>>>>=20 >>>>>>>>> [1] http://dbeaver.jkiss.org/ >>>>>>>>> [2] https://issues.apache.org/jira/browse/IGNITE-6048 >>>>>>>>> [3] https://issues.apache.org/jira/browse/IGNITE-6046 >>>>>>>>> [4] https://issues.apache.org/jira/browse/IGNITE-6047 >>>>>>>>> [5] https://issues.apache.org/jira/browse/IGNITE-5233 >>>>>>>>>=20 >>>>>>>>> D. >>>>>>>>>=20 >>>>>>=20 >>>>=20 >>=20 >=20 > --=20 > Taras Ledkov > Mail-To: tledkov@gridgain.com >=20