You can mix both "optimistic" and "pessimistic" reads in a single transaction. This is one of the main points of proposed API. Normally users do not define blocking behavior on TX level. They do that on per-operation level.
On Fri, Sep 29, 2017 at 3:30 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > On Thu, Sep 28, 2017 at 10:30 PM, Vladimir Ozerov <voze...@gridgain.com> > wrote: > > > Dima, > > > > IgniteCache.withReadForUpdate() :-) > > > > And how is it better than a pessimistic transaction with read? >
