SQL usability issues

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

SQL usability issues

dsetrakyan
Igniters,

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:

   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.

The links to the tickets are below.

[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

D.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL usability issues

Denis Magda
Dmitriy,

That's the documentation that shows how to configure Pentaho via JDBC:
https://apacheignite-tools.readme.io/v2.1/docs/pentaho

Plus on the tools' domain you can see Tableau based ODBC example.

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.

Denis

On Friday, August 11, 2017, Dmitriy Setrakyan <[hidden email]> wrote:

> Igniters,
>
> 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:
>
>    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.
>
> The links to the tickets are below.
>
> [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
>
> D.
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL usability issues

dsetrakyan
On Fri, Aug 11, 2017 at 7:31 PM, Denis Magda <[hidden email]> wrote:

> Dmitriy,
>
> That's the documentation that shows how to configure Pentaho via JDBC:
> https://apacheignite-tools.readme.io/v2.1/docs/pentaho


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.


>
>
> Plus on the tools' domain you can see Tableau based ODBC example.
>
> 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.
>
> Denis
>
> On Friday, August 11, 2017, Dmitriy Setrakyan <[hidden email]>
> wrote:
>
> > Igniters,
> >
> > 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:
> >
> >    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.
> >
> > The links to the tickets are below.
> >
> > [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
> >
> > D.
> >
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL usability issues

Igor Sapego-2
Dmitriy,

But what would we put in such generic section?

Best Regards,
Igor

On Sun, Aug 13, 2017 at 7:20 PM, Dmitriy Setrakyan <[hidden email]>
wrote:

> On Fri, Aug 11, 2017 at 7:31 PM, Denis Magda <[hidden email]> wrote:
>
> > Dmitriy,
> >
> > That's the documentation that shows how to configure Pentaho via JDBC:
> > https://apacheignite-tools.readme.io/v2.1/docs/pentaho
>
>
> 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.
>
>
> >
> >
> > Plus on the tools' domain you can see Tableau based ODBC example.
> >
> > 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.
> >
> > Denis
> >
> > On Friday, August 11, 2017, Dmitriy Setrakyan <[hidden email]>
> > wrote:
> >
> > > Igniters,
> > >
> > > 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:
> > >
> > >    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.
> > >
> > > The links to the tickets are below.
> > >
> > > [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
> > >
> > > D.
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL usability issues

dsetrakyan
On Mon, Aug 14, 2017 at 2:52 AM, Igor Sapego <[hidden email]> wrote:

> Dmitriy,
>
> But what would we put in such generic section?
>

- JAR in Ignite that contains JDBC driver
- connection string
- port (with explanation how to change it)
- username/password with explanation why Ignite does not require it.
- screenshot of configuring these properties with a popular SQL tool


>
> Best Regards,
> Igor
>
> On Sun, Aug 13, 2017 at 7:20 PM, Dmitriy Setrakyan <[hidden email]>
> wrote:
>
> > On Fri, Aug 11, 2017 at 7:31 PM, Denis Magda <[hidden email]>
> wrote:
> >
> > > Dmitriy,
> > >
> > > That's the documentation that shows how to configure Pentaho via JDBC:
> > > https://apacheignite-tools.readme.io/v2.1/docs/pentaho
> >
> >
> > 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.
> >
> >
> > >
> > >
> > > Plus on the tools' domain you can see Tableau based ODBC example.
> > >
> > > 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.
> > >
> > > Denis
> > >
> > > On Friday, August 11, 2017, Dmitriy Setrakyan <[hidden email]>
> > > wrote:
> > >
> > > > Igniters,
> > > >
> > > > 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:
> > > >
> > > >    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.
> > > >
> > > > The links to the tickets are below.
> > > >
> > > > [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
> > > >
> > > > D.
> > > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL usability issues

Denis Magda-2
In reply to this post by dsetrakyan
Igniters,

I’ve prepared the getting started basing on DBeaver tool:
https://apacheignite-tools.readme.io/docs/dbeaver <https://apacheignite-tools.readme.io/docs/dbeaver>

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>

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>

*Alexander P.*, *Vladimir*, how difficult is to support this feature?


Denis

> On Aug 13, 2017, at 9:20 AM, Dmitriy Setrakyan <[hidden email]> wrote:
>
> On Fri, Aug 11, 2017 at 7:31 PM, Denis Magda <[hidden email]> wrote:
>
>> Dmitriy,
>>
>> That's the documentation that shows how to configure Pentaho via JDBC:
>> https://apacheignite-tools.readme.io/v2.1/docs/pentaho
>
>
> 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.
>
>
>>
>>
>> Plus on the tools' domain you can see Tableau based ODBC example.
>>
>> 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.
>>
>> Denis
>>
>> On Friday, August 11, 2017, Dmitriy Setrakyan <[hidden email]>
>> wrote:
>>
>>> Igniters,
>>>
>>> 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:
>>>
>>>   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.
>>>
>>> The links to the tickets are below.
>>>
>>> [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
>>>
>>> D.
>>>
>>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL usability issues

Valentin Kulichenko
Denis,

I think this article should be more generic, describing how to connect a
generic JDBC tool to Ignite (probably using DBeaver as an example).

Right now it looks like out of all such tools we support only DBeaver for
some reason :)

What do you think?

-Val

On Wed, Aug 16, 2017 at 1:49 PM, Denis Magda <[hidden email]> wrote:

> Igniters,
>
> I’ve prepared the getting started basing on DBeaver tool:
> https://apacheignite-tools.readme.io/docs/dbeaver <
> https://apacheignite-tools.readme.io/docs/dbeaver>
>
> 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>
>
> 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>
>
> *Alexander P.*, *Vladimir*, how difficult is to support this feature?
>
> —
> Denis
>
> > On Aug 13, 2017, at 9:20 AM, Dmitriy Setrakyan <[hidden email]>
> wrote:
> >
> > On Fri, Aug 11, 2017 at 7:31 PM, Denis Magda <[hidden email]>
> wrote:
> >
> >> Dmitriy,
> >>
> >> That's the documentation that shows how to configure Pentaho via JDBC:
> >> https://apacheignite-tools.readme.io/v2.1/docs/pentaho
> >
> >
> > 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.
> >
> >
> >>
> >>
> >> Plus on the tools' domain you can see Tableau based ODBC example.
> >>
> >> 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.
> >>
> >> Denis
> >>
> >> On Friday, August 11, 2017, Dmitriy Setrakyan <[hidden email]>
> >> wrote:
> >>
> >>> Igniters,
> >>>
> >>> 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:
> >>>
> >>>   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.
> >>>
> >>> The links to the tickets are below.
> >>>
> >>> [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
> >>>
> >>> D.
> >>>
> >>
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL usability issues

Denis Magda-2
Val,

This article is generic:
https://apacheignite.readme.io/docs/getting-started-sql <https://apacheignite.readme.io/docs/getting-started-sql>

DBeaver, Pentaho and Tableau are given as examples.

If the description or introduction of the tool should sound clearer please suggest your version.


Denis
 

> On Aug 16, 2017, at 5:55 PM, Valentin Kulichenko <[hidden email]> wrote:
>
> Denis,
>
> I think this article should be more generic, describing how to connect a
> generic JDBC tool to Ignite (probably using DBeaver as an example).
>
> Right now it looks like out of all such tools we support only DBeaver for
> some reason :)
>
> What do you think?
>
> -Val
>
> On Wed, Aug 16, 2017 at 1:49 PM, Denis Magda <[hidden email]> wrote:
>
>> Igniters,
>>
>> I’ve prepared the getting started basing on DBeaver tool:
>> https://apacheignite-tools.readme.io/docs/dbeaver <
>> https://apacheignite-tools.readme.io/docs/dbeaver>
>>
>> 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>
>>
>> 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>
>>
>> *Alexander P.*, *Vladimir*, how difficult is to support this feature?
>>
>> —
>> Denis
>>
>>> On Aug 13, 2017, at 9:20 AM, Dmitriy Setrakyan <[hidden email]>
>> wrote:
>>>
>>> On Fri, Aug 11, 2017 at 7:31 PM, Denis Magda <[hidden email]>
>> wrote:
>>>
>>>> Dmitriy,
>>>>
>>>> That's the documentation that shows how to configure Pentaho via JDBC:
>>>> https://apacheignite-tools.readme.io/v2.1/docs/pentaho
>>>
>>>
>>> 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.
>>>
>>>
>>>>
>>>>
>>>> Plus on the tools' domain you can see Tableau based ODBC example.
>>>>
>>>> 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.
>>>>
>>>> Denis
>>>>
>>>> On Friday, August 11, 2017, Dmitriy Setrakyan <[hidden email]>
>>>> wrote:
>>>>
>>>>> Igniters,
>>>>>
>>>>> 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:
>>>>>
>>>>>  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.
>>>>>
>>>>> The links to the tickets are below.
>>>>>
>>>>> [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
>>>>>
>>>>> D.
>>>>>
>>>>
>>
>>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL usability issues

dsetrakyan
Denis,

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.

D.

On Wed, Aug 16, 2017 at 6:01 PM, Denis Magda <[hidden email]> wrote:

> Val,
>
> This article is generic:
> https://apacheignite.readme.io/docs/getting-started-sql <
> https://apacheignite.readme.io/docs/getting-started-sql>
>
> DBeaver, Pentaho and Tableau are given as examples.
>
> If the description or introduction of the tool should sound clearer please
> suggest your version.
>
> —
> Denis
>
> > On Aug 16, 2017, at 5:55 PM, Valentin Kulichenko <
> [hidden email]> wrote:
> >
> > Denis,
> >
> > I think this article should be more generic, describing how to connect a
> > generic JDBC tool to Ignite (probably using DBeaver as an example).
> >
> > Right now it looks like out of all such tools we support only DBeaver for
> > some reason :)
> >
> > What do you think?
> >
> > -Val
> >
> > On Wed, Aug 16, 2017 at 1:49 PM, Denis Magda <[hidden email]> wrote:
> >
> >> Igniters,
> >>
> >> I’ve prepared the getting started basing on DBeaver tool:
> >> https://apacheignite-tools.readme.io/docs/dbeaver <
> >> https://apacheignite-tools.readme.io/docs/dbeaver>
> >>
> >> 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>
> >>
> >> 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>
> >>
> >> *Alexander P.*, *Vladimir*, how difficult is to support this feature?
> >>
> >> —
> >> Denis
> >>
> >>> On Aug 13, 2017, at 9:20 AM, Dmitriy Setrakyan <[hidden email]>
> >> wrote:
> >>>
> >>> On Fri, Aug 11, 2017 at 7:31 PM, Denis Magda <[hidden email]>
> >> wrote:
> >>>
> >>>> Dmitriy,
> >>>>
> >>>> That's the documentation that shows how to configure Pentaho via JDBC:
> >>>> https://apacheignite-tools.readme.io/v2.1/docs/pentaho
> >>>
> >>>
> >>> 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.
> >>>
> >>>
> >>>>
> >>>>
> >>>> Plus on the tools' domain you can see Tableau based ODBC example.
> >>>>
> >>>> 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.
> >>>>
> >>>> Denis
> >>>>
> >>>> On Friday, August 11, 2017, Dmitriy Setrakyan <[hidden email]>
> >>>> wrote:
> >>>>
> >>>>> Igniters,
> >>>>>
> >>>>> 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:
> >>>>>
> >>>>>  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.
> >>>>>
> >>>>> The links to the tickets are below.
> >>>>>
> >>>>> [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
> >>>>>
> >>>>> D.
> >>>>>
> >>>>
> >>
> >>
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL usability issues

Denis Magda-2
No I see what you tried to convey. Here it is the doc:
https://apacheignite.readme.io/docs/sql-tooling <https://apacheignite.readme.io/docs/sql-tooling>


Denis

> On Aug 16, 2017, at 6:06 PM, Dmitriy Setrakyan <[hidden email]> wrote:
>
> Denis,
>
> 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.
>
> D.
>
> On Wed, Aug 16, 2017 at 6:01 PM, Denis Magda <[hidden email]> wrote:
>
>> Val,
>>
>> This article is generic:
>> https://apacheignite.readme.io/docs/getting-started-sql <
>> https://apacheignite.readme.io/docs/getting-started-sql>
>>
>> DBeaver, Pentaho and Tableau are given as examples.
>>
>> If the description or introduction of the tool should sound clearer please
>> suggest your version.
>>
>> —
>> Denis
>>
>>> On Aug 16, 2017, at 5:55 PM, Valentin Kulichenko <
>> [hidden email]> wrote:
>>>
>>> Denis,
>>>
>>> I think this article should be more generic, describing how to connect a
>>> generic JDBC tool to Ignite (probably using DBeaver as an example).
>>>
>>> Right now it looks like out of all such tools we support only DBeaver for
>>> some reason :)
>>>
>>> What do you think?
>>>
>>> -Val
>>>
>>> On Wed, Aug 16, 2017 at 1:49 PM, Denis Magda <[hidden email]> wrote:
>>>
>>>> Igniters,
>>>>
>>>> I’ve prepared the getting started basing on DBeaver tool:
>>>> https://apacheignite-tools.readme.io/docs/dbeaver <
>>>> https://apacheignite-tools.readme.io/docs/dbeaver>
>>>>
>>>> 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>
>>>>
>>>> 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>
>>>>
>>>> *Alexander P.*, *Vladimir*, how difficult is to support this feature?
>>>>
>>>> —
>>>> Denis
>>>>
>>>>> On Aug 13, 2017, at 9:20 AM, Dmitriy Setrakyan <[hidden email]>
>>>> wrote:
>>>>>
>>>>> On Fri, Aug 11, 2017 at 7:31 PM, Denis Magda <[hidden email]>
>>>> wrote:
>>>>>
>>>>>> Dmitriy,
>>>>>>
>>>>>> That's the documentation that shows how to configure Pentaho via JDBC:
>>>>>> https://apacheignite-tools.readme.io/v2.1/docs/pentaho
>>>>>
>>>>>
>>>>> 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.
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>> Plus on the tools' domain you can see Tableau based ODBC example.
>>>>>>
>>>>>> 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.
>>>>>>
>>>>>> Denis
>>>>>>
>>>>>> On Friday, August 11, 2017, Dmitriy Setrakyan <[hidden email]>
>>>>>> wrote:
>>>>>>
>>>>>>> Igniters,
>>>>>>>
>>>>>>> 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:
>>>>>>>
>>>>>>> 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.
>>>>>>>
>>>>>>> The links to the tickets are below.
>>>>>>>
>>>>>>> [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
>>>>>>>
>>>>>>> D.
>>>>>>>
>>>>>>
>>>>
>>>>
>>
>>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SQL usability issues

dsetrakyan
On Thu, Aug 17, 2017 at 2:22 PM, Denis Magda <[hidden email]> wrote:

> No I see what you tried to convey. Here it is the doc:
> https://apacheignite.readme.io/docs/sql-tooling <
> https://apacheignite.readme.io/docs/sql-tooling>
>

Looks very nice. I think we should separate all the SQL-related
documentation into its own separate SQL section.


> —
> Denis
>
> > On Aug 16, 2017, at 6:06 PM, Dmitriy Setrakyan <[hidden email]>
> wrote:
> >
> > Denis,
> >
> > 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.
> >
> > D.
> >
> > On Wed, Aug 16, 2017 at 6:01 PM, Denis Magda <[hidden email]> wrote:
> >
> >> Val,
> >>
> >> This article is generic:
> >> https://apacheignite.readme.io/docs/getting-started-sql <
> >> https://apacheignite.readme.io/docs/getting-started-sql>
> >>
> >> DBeaver, Pentaho and Tableau are given as examples.
> >>
> >> If the description or introduction of the tool should sound clearer
> please
> >> suggest your version.
> >>
> >> —
> >> Denis
> >>
> >>> On Aug 16, 2017, at 5:55 PM, Valentin Kulichenko <
> >> [hidden email]> wrote:
> >>>
> >>> Denis,
> >>>
> >>> I think this article should be more generic, describing how to connect
> a
> >>> generic JDBC tool to Ignite (probably using DBeaver as an example).
> >>>
> >>> Right now it looks like out of all such tools we support only DBeaver
> for
> >>> some reason :)
> >>>
> >>> What do you think?
> >>>
> >>> -Val
> >>>
> >>> On Wed, Aug 16, 2017 at 1:49 PM, Denis Magda <[hidden email]>
> wrote:
> >>>
> >>>> Igniters,
> >>>>
> >>>> I’ve prepared the getting started basing on DBeaver tool:
> >>>> https://apacheignite-tools.readme.io/docs/dbeaver <
> >>>> https://apacheignite-tools.readme.io/docs/dbeaver>
> >>>>
> >>>> 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>
> >>>>
> >>>> 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>
> >>>>
> >>>> *Alexander P.*, *Vladimir*, how difficult is to support this feature?
> >>>>
> >>>> —
> >>>> Denis
> >>>>
> >>>>> On Aug 13, 2017, at 9:20 AM, Dmitriy Setrakyan <
> [hidden email]>
> >>>> wrote:
> >>>>>
> >>>>> On Fri, Aug 11, 2017 at 7:31 PM, Denis Magda <[hidden email]>
> >>>> wrote:
> >>>>>
> >>>>>> Dmitriy,
> >>>>>>
> >>>>>> That's the documentation that shows how to configure Pentaho via
> JDBC:
> >>>>>> https://apacheignite-tools.readme.io/v2.1/docs/pentaho
> >>>>>
> >>>>>
> >>>>> 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.
> >>>>>
> >>>>>
> >>>>>>
> >>>>>>
> >>>>>> Plus on the tools' domain you can see Tableau based ODBC example.
> >>>>>>
> >>>>>> 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.
> >>>>>>
> >>>>>> Denis
> >>>>>>
> >>>>>> On Friday, August 11, 2017, Dmitriy Setrakyan <
> [hidden email]>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Igniters,
> >>>>>>>
> >>>>>>> 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:
> >>>>>>>
> >>>>>>> 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.
> >>>>>>>
> >>>>>>> The links to the tickets are below.
> >>>>>>>
> >>>>>>> [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
> >>>>>>>
> >>>>>>> D.
> >>>>>>>
> >>>>>>
> >>>>
> >>>>
> >>
> >>
>
>
Loading...