Hi, Very new to Ignite and just trying to assess its capabilities.
tl;dr: are optimistic serializable sql transactions on the roadmap? It seems that currently only pessimistic repeatable_read sql transactions are supported (in beta as of the current version -- 2.7). I'm trying to confirm that, in Ignite, if I started two concurrent transactions (from the same snapshot) where one intends to execute statements #1 (compare-and-set), #2 (read-only), and #3 (whatever else), while the other intends to execute the exact same update statements #1, #2, and #3, but also a subsequent #4, understanding that (all but) one of those transactions would probably fail to commit, I'm looking to clarify whether or not the failing one would throw/abort even before reaching statement #2 (which might be a read returning values)? If I'm reading the docs correctly it seems that in pessimistic repeatable_read mode the transaction would fail one of the transactions at statement #1 (due to write conflict), but if it could have been optimistic serializable, the transaction would simply rollback at the point a commit was attempted. Please correct me if I'm wrong. Lastly, are optimistic serializable sql transactions on the roadmap? Thanks
