Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <1479404050670-9055.post@n6.nabble.com>
References: <1479304724484-9018.post@n6.nabble.com> <1479328516749-9029.post@n6.nabble.com>
 <1479383128261-9042.post@n6.nabble.com> <1479397963122-9053.post@n6.nabble.com>
 <1479404050670-9055.post@n6.nabble.com>
From: Alexey Goncharuk <alexey.goncharuk@gmail.com>
Date: Thu, 17 Nov 2016 20:57:04 +0300
Message-ID: <CABDss3iHSCRPSn82qi0r-MDhWzAueLgDAFX6wwic+qD+EoraXQ@mail.gmail.com>
Subject: Re: Order of transaction commit, cache update and event listener notification
To: user@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a114db026d17a71054182eae8
archived-at: Thu, 17 Nov 2016 17:57:09 -0000

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

Hi,

Currently SQL queries do not participate in transactions in any way, so you
can see partially committed data from other transactions.

In other words, if a thread 1 updates keys 1, 2, 3, 4 and started
transaction commit, and thread 2 issues an SQL query, this query may see
keys 1, 2 updated and keys 3, 4 - not.

As Vlad mentioned, there is a ticket for supporting transactional SQL [1]
which you can track (and join discussion regarding the design, btw).

Hope this helps,
AG


[1] https://issues.apache.org/jira/browse/IGNITE-3478

2016-11-17 20:34 GMT+03:00 newbie <lists.my@gmail.com>:

> Thanks for the info and link.
>
> Just an add-on question based on the link:
>
> Do the sql queries really see another transaction's dirty data with
> OPTIMISTIC, REPEATABLE_READ ?
>
> From my testing it seems like if we are writing from transaction T1 and
> reading from a different thread in transaction T2, I don't really see Sql
> query returning uncommitted data from T1. Have I missed something here ?
>
>
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Order-of-transaction-commit-cache-
> update-and-event-listener-notification-tp9018p9055.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

--001a114db026d17a71054182eae8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>Currently SQL queries do not partic=
ipate in transactions in any way, so you can see partially committed data f=
rom other transactions.=C2=A0</div><div><br></div><div>In other words, if a=
 thread 1 updates keys 1, 2, 3, 4 and started transaction commit, and threa=
d 2 issues an SQL query, this query may see keys 1, 2 updated and keys 3, 4=
 - not.</div><div><br></div><div>As Vlad mentioned, there is a ticket for s=
upporting transactional SQL [1] which you can track (and join discussion re=
garding the design, btw).</div><div><br></div><div>Hope this helps,</div><d=
iv>AG</div><div><br></div><div><br></div><div>[1] <a href=3D"https://issues=
.apache.org/jira/browse/IGNITE-3478">https://issues.apache.org/jira/browse/=
IGNITE-3478</a></div></div><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">2016-11-17 20:34 GMT+03:00 newbie <span dir=3D"ltr">&lt;<a href=
=3D"mailto:lists.my@gmail.com" target=3D"_blank">lists.my@gmail.com</a>&gt;=
</span>:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">Thanks for the info and link.<br=
>
<br>
Just an add-on question based on the link:<br>
<br>
Do the sql queries really see another transaction&#39;s dirty data with<br>
OPTIMISTIC, REPEATABLE_READ ?<br>
<br>
From my testing it seems like if we are writing from transaction T1 and<br>
reading from a different thread in transaction T2, I don&#39;t really see S=
ql<br>
query returning uncommitted data from T1. Have I missed something here ?<br=
>
<br>
<br>
<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href=3D"http://apache-ignite-users.70518.x=
6.nabble.com/Order-of-transaction-commit-cache-update-and-event-listener-no=
tification-tp9018p9055.html" rel=3D"noreferrer" target=3D"_blank">http://ap=
ache-ignite-users.<wbr>70518.x6.nabble.com/Order-of-<wbr>transaction-commit=
-cache-<wbr>update-and-event-listener-<wbr>notification-tp9018p9055.html</a=
><br>
<div class=3D"HOEnZb"><div class=3D"h5">Sent from the Apache Ignite Users m=
ailing list archive at Nabble.com.<br>
</div></div></blockquote></div><br></div>

--001a114db026d17a71054182eae8--