Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
References: <CAGt6o8=BbaWFuFupsfojj5AhmPgeKmrUgG0ZkRg0iT3T0q9LAA@mail.gmail.com>
 <00C87F50-24B8-44F6-8EE3-A44C663A6818@apache.org> <CAGt6o8khWvsnHNi05oudVKXqOG1r0Emwt83_JZn1fYPOmWuWGQ@mail.gmail.com>
 <00036EC0-6228-4764-BF35-04596E86F957@apache.org> <CA+0=VoXnvT3A-r5Kkj_BLd7LjFX8QC4_1shMV-J0_Tk80O+6=A@mail.gmail.com>
 <CAGt6o8mu_SwqvRVE51iN50KT5kkMVWOKy=_0=W5VS8wMbHqv6w@mail.gmail.com> <CA+0=VoWexG=XWR=JfbPwm0a7iEC4VPjwCieQ4Y0rv=uyobPUEg@mail.gmail.com>
In-Reply-To: <CA+0=VoWexG=XWR=JfbPwm0a7iEC4VPjwCieQ4Y0rv=uyobPUEg@mail.gmail.com>
From: Vladimir Ozerov <vozerov@gridgain.com>
Date: Sun, 15 Oct 2017 07:27:02 +0000
Message-ID: <CAGt6o8kfGfEXEUpDLXPMb+n3EFGR6eNAA6M0W2HWZwG2rUrqag@mail.gmail.com>
Subject: Re: Optimized DML execution: how to name it?
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary="94eb2c14a21e96a3d4055b90d12e"
archived-at: Sun, 15 Oct 2017 07:27:20 -0000

--94eb2c14a21e96a3d4055b90d12e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

No, it is not exposed to public API. Didn't want to add another flag to
SqlFieldsQuery.

=D0=B2=D1=81, 15 =D0=BE=D0=BA=D1=82. 2017 =D0=B3. =D0=B2 0:19, Dmitriy Setr=
akyan <dsetrakyan@apache.org>:

> Vova, is there any way to enable this flag from API, without using JDBC
> driver?
>
> On Sat, Oct 14, 2017 at 1:17 PM, Vladimir Ozerov <vozerov@gridgain.com>
> wrote:
>
> > Dmitry,
> >
> > Corretct. Example: jdbc:ignite:thin://
> 192.168.0.1?skipReducerOnClient=3Dtrue
> >
> > On Fri, Oct 13, 2017 at 8:16 PM, Dmitriy Setrakyan <
> dsetrakyan@apache.org>
> > wrote:
> >
> > > Vova,
> > >
> > > Just to make sure, we are not adding a new configuration property,
> right?
> > > Is this just a JDBC connection flag we are discussing? If yes, can yo=
u
> > > please provide an example of the JDBC connection string?
> > >
> > > D.
> > >
> > > On Fri, Oct 13, 2017 at 9:57 AM, Denis Magda <dmagda@apache.org>
> wrote:
> > >
> > > > Vladimir,
> > > >
> > > > > "inPlaceUpdate" is not very good candidate because there are a lo=
t
> of
> > > > other
> > > > > "in place update" optimizations in RDBMS word, and most of them
> > relates
> > > > to
> > > > > in-place update of some value in the data page. I am afraid users
> > will
> > > be
> > > > > confused with this name.
> > > >
> > > > I=E2=80=99m not insisting on this name but that=E2=80=99s neither s=
ystem nor global
> > > > configuration property. The property scope is defined by the
> drivers=E2=80=99s
> > > > boundaries. So if to think of it as of a hint for the drivers it
> > doesn=E2=80=99t
> > > > sound too generic.
> > > >
> > > > Anyway, =E2=80=9Creducer=E2=80=9D versions sound too low-level and,=
 probably, I would
> > > > leave the current =E2=80=9CupdateOnServer=E2=80=9D as is.
> > > >
> > > > =E2=80=94
> > > > Denis
> > > >
> > > > > On Oct 13, 2017, at 12:02 AM, Vladimir Ozerov <
> vozerov@gridgain.com>
> > > > wrote:
> > > > >
> > > > > Denis,
> > > > >
> > > > > In future SQL transactional protocol will do all updates "in plac=
e"
> > > > instead
> > > > > of passing it to the client. This is the only possible way to
> perform
> > > > large
> > > > > updates without killing the client with OOME.
> > > > > "inPlaceUpdate" is not very good candidate because there are a lo=
t
> of
> > > > other
> > > > > "in place update" optimizations in RDBMS word, and most of them
> > relates
> > > > to
> > > > > in-place update of some value in the data page. I am afraid users
> > will
> > > be
> > > > > confused with this name.
> > > > >
> > > > > On Fri, Oct 13, 2017 at 2:15 AM, Denis Magda <dmagda@apache.org>
> > > wrote:
> > > > >
> > > > >> How about =E2=80=9CinPlaceUpdate=E2=80=9D?
> > > > >>
> > > > >> A side note, I see the feature documented for ODBC in our hidden
> SQL
> > > > >> domain [1]. But it=E2=80=99s missing for JDBC. Did we forget to =
update the
> > > JDBC
> > > > >> docs?
> > > > >>
> > > > >> [1] https://apacheignite-sql.readme.io/docs/connection-
> > > > >> string-and-dsn#section-supported-arguments
> > > > >>
> > > > >>>
> > > > >>> Unfortunately we cannot enable this mode by default, because it
> is
> > > > still
> > > > >> a
> > > > >>> bit raw and there is a risk of regressions. Also when
> transactional
> > > SQL
> > > > >> is
> > > > >>> ready this feature will make no sense in TX mode. For this reas=
on
> > we
> > > > >>> disable it by default for now
> > > > >>
> > > > >>
> > > > >> Does it mean that this kind of optimization is not feasible for
> > > > >> transaction SQL or it will be just solved differently? Just tryi=
ng
> > to
> > > > grasp
> > > > >> if we are going to drop it after the TX SQL release.
> > > > >>
> > > > >> =E2=80=94
> > > > >> Denis
> > > > >>
> > > > >>> On Oct 11, 2017, at 11:45 PM, Vladimir Ozerov <
> > vozerov@gridgain.com>
> > > > >> wrote:
> > > > >>>
> > > > >>> Igniters,
> > > > >>>
> > > > >>> We prepared optimization of DML processing. Instead of passing
> all
> > > data
> > > > >>> being updated through the client node, now we can optionally se=
nd
> > SQL
> > > > >>> statement to data nodes and perform update locally. This could
> > > greatly
> > > > >>> improve performance of certain DML operations.
> > > > >>>
> > > > >>> Unfortunately we cannot enable this mode by default, because it
> is
> > > > still
> > > > >> a
> > > > >>> bit raw and there is a risk of regressions. Also when
> transactional
> > > SQL
> > > > >> is
> > > > >>> ready this feature will make no sense in TX mode. For this reas=
on
> > we
> > > > >>> disable it by default for now.
> > > > >>>
> > > > >>> It will be possible to enable it from JDBC/ODBC drivers using a
> > flag.
> > > > >>> Question - how to name this flag? Current name is
> > > "*updateOnServer*". I
> > > > >>> doesn't like it much, but cannot do better. Please share other
> > ideas.
> > > > >>>
> > > > >>> - "distributedDml"? No, every operation is distributed.
> > > > >>> - "serverDml"?
> > > > >>>
> > > > >>> Vladimir.
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
>

--94eb2c14a21e96a3d4055b90d12e--