Re: SQL usability issues

Thanks Taras, fixed the doc. Not sure how it worked before with the wrong name. — Denis > On Aug 21, 2017, at 5:05 AM, Taras Ledkov wrote: > > Hi, > > Denis, please rename '|IgniteThinJdbcDriver| ' -> 'IgniteJdbcThinDriver' an > the Installation and Configuration section (see [1]). > > [1]

Re: SQL usability issues

Hi, Denis, please rename '|IgniteThinJdbcDriver| ' -> 'IgniteJdbcThinDriver' an the Installation and Configuration section (see [1]). [1] https://apacheignite.readme.io/docs/sql-tooling#installation-and-configuration On 18.08.2017 0:22, Denis Magda wrote: No I see what you tried to convey

Re: SQL usability issues

On Thu, Aug 17, 2017 at 2:22 PM, Denis Magda 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

Re: SQL usability issues

No I see what you tried to convey. Here it is the doc: https://apacheignite.readme.io/docs/sql-tooling — Denis > On Aug 16, 2017, at 6:06 PM, Dmitriy Setrakyan wrote: > > Denis, > > I agree with Val. I am OK with using DBeaver as an example, b

Re: SQL usability issues

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 wrote: >

Re: SQL usability issues

Val, This article is generic: 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.

Re: SQL usability issues

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,

Re: SQL usability issues

Igniters, I’ve prepared the getting started basing on DBeaver tool: 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

Re: SQL usability issues

On Mon, Aug 14, 2017 at 2:52 AM, Igor Sapego 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. - scre

Re: SQL usability issues

Dmitriy, But what would we put in such generic section? Best Regards, Igor On Sun, Aug 13, 2017 at 7:20 PM, Dmitriy Setrakyan wrote: > On Fri, Aug 11, 2017 at 7:31 PM, Denis Magda wrote: > > > Dmitriy, > > > > That's the documentation that shows how to configure Pentaho via JDBC: > > https://

Re: SQL usability issues

On Fri, Aug 11, 2017 at 7:31 PM, Denis Magda 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 SQ

Re: SQL usability issues

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

SQL usability issues

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 multi