Yakov, My vote goes for the current behavior - an atomic operation is applied right away if it’s a part of a transaction. It’s better not to break compatibility here, there are already to many incompatible changes in 2.0.
— Denis > On Mar 28, 2017, at 3:08 AM, Yakov Zhdanov <yzhda...@apache.org> wrote: > > As far as I know operations on atomic caches are applied immediately > dishonoring any tx context. > > I would suggest that atomic cache update operation called from active tx > throws illegal state exception, unless user intentionally permits this > update by calling atomicCache.withAllowInTx() (similar to withSkipStore()). > > Thoughts? > > --Yakov
