ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Future of Ignite transactions
Date Fri, 29 Sep 2017 22:29:46 GMT
On Fri, Sep 29, 2017 at 6:10 AM, Vladimir Ozerov <vozerov@gridgain.com>

> Dima,
> I doubt you ever heard from users "we need snapshot isolation" because this
> is implementation detail, rather than public behavior :-)

Believe me, I have. People want to make sure that the data is not changed
from the call to tx.start(...). What we have, is making sure that it does
not change after it has been accessed the 1st time.

This is not an implementation detail, this is a different transaction

> I already explained what we are fixing - broken TX API. 6 possible modes, 5
> real modes, 2 broken modes (OPT+RC, OPT+RR), and only *two (!!!)* modes
> which are really used in practice (PES+RR, OPT+SER). Do you still think it
> is not broken?

I have not seen any clean proposal yet. I do not want to break it even more

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message