Igniters, Our docs say that DML statements are executed outside of current transaction. This is not true - it is enlisted into transaction at the moment. We need to fix that, but how?
Possible solutions: 1) Execute DML outside of TX, similar to current IgniteCache#getAllOutTx 2) Or throw an exception - DML cannot be executed inside TX at all I prefer the second. For now DML inside TX simply doesn't make sense. It is prone to deadlocks and has unpredictable semantics. Let's restrict it explicitly. Thoughts? Vladimir.
