Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <CAEOB7kWFWw_-8cALy+n29J=BbA8ZKs93NZ_87GBpaqcChwdt9A@mail.gmail.com>
References: <CAFx+i-ZDgoYjDE6U=ohr_GC8avX11dR7QWXBAhwcJcJ2RNzoMQ@mail.gmail.com>
 <CA+eZwrEou+wqnJ_0kknDzOqQNsbR8osT_-=519d=Rmfha70T3A@mail.gmail.com> <CAEOB7kWFWw_-8cALy+n29J=BbA8ZKs93NZ_87GBpaqcChwdt9A@mail.gmail.com>
From: Alexey Kuznetsov <akuznetsov@gridgain.com>
Date: Mon, 25 Jul 2016 14:41:06 +0700
Message-ID: <CALH+G9pMWv=nCk7OLy33-CwRPo+xcP6ua9Q3=NHvX9OGCpdkpA@mail.gmail.com>
Subject: Re: Distributed joins for JDBC
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a114a69ea3f309b053870e815
archived-at: Mon, 25 Jul 2016 07:41:13 -0000

--001a114a69ea3f309b053870e815
Content-Type: text/plain; charset=UTF-8

Why we need to *TURN ON/OFF* this mode?
Why not have it always *ON*?

On Mon, Jul 25, 2016 at 2:32 PM, Andrey Gura <agura@gridgain.com> wrote:

> Our JDBC drivers already have connection properties that correspond to
> SqlFieldsQuery properties. So we can just add support of this parameter to
> connection string parser.
>
> Corresponding ticket created IGNITE-3563 (
> https://issues.apache.org/jira/browse/IGNITE-3563 ).
>
> On Mon, Jul 25, 2016 at 10:04 AM, Sergi Vladykin <sergi.vladykin@gmail.com
> >
> wrote:
>
> > I don't think it makes sense to extend JDBC this way because usually if
> one
> > have access to Java API he most probably will use Ignite API. If for some
> > reason they use JDBC it means that it is an application which was aimed
> to
> > work with any RDBMS and should not know about quirks of some particular
> > driver. Take any JDBC based SQL console for example, we have to support
> > them out of the box.
> >
> > I think we should have a connection options which we can append to JDBC
> URL
> > like it is done in H2:
> >
> > jdbc:h2:my_database;OPTION1=bla;OPTION2=blabla
> >
> > In our case it must be something like DISTRIBUTED_JOINS=true and it will
> > affect the whole connection.
> >
> > Of course we have to support simultaneous connections to the same DB with
> > different options.
> >
> > Sergi
> >
> >
> > 2016-07-25 9:19 GMT+03:00 Semyon Boikov <sboikov@apache.org>:
> >
> > > Hi,
> > >
> > > Last week distributed joins functionality was merged, but one thing was
> > > overlooked. Distributed joins should be explicitly enabled using using
> > > method 'setDistributedJoins' available in java API
> > > (SqlQuery/SqlFieldsQuery). First, this parameter should be also added
> in
> > > .Net/C++/REST API, this is straightforward. Also there should be
> > > possibility to enable distributed joins for JDBC API. Does it make
> sense
> > to
> > > add Ignite-specific interface extending standard java.sql.Statement, so
> > > 'setDistributedJoins' method can be added there.
> > > JDBC API already have 'unwrap' method to deal with vendor-specific
> > > interfaces, code will look like this:
> > > * IgniteStatement stmt =
> > > connection.createStatement().unwrap(IgniteStatement.class);*
> > > * stmt.setDistributedJoins(true);*
> > > *        stmt.executeQuery("...");*
> > >
> > > What do you think?
> > >
> >
>
>
>
> --
> Andrey Gura
> GridGain Systems, Inc.
> www.gridgain.com
>


-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

--001a114a69ea3f309b053870e815--