[
https://issues.apache.org/jira/browse/IGNITE-9622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689256#comment-16689256
]
Ivan Pavlukhin commented on IGNITE-9622:
----------------------------------------
[~gvvinblade] If I get your point right it is already works in that way.
{{MvccUtils.currentTx}} throwing new exceptions is not used by SQL components
directly. SQL uses various {{MvccUtils.tx}} methods which translate exceptions
to {{IgniteSQLException}} with corresponding _status code_.
> MVCC Cache API: prohibit non PESSIMISTIC REPEATABLE_READ transactions
> ---------------------------------------------------------------------
>
> Key: IGNITE-9622
> URL: https://issues.apache.org/jira/browse/IGNITE-9622
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Ivan Pavlukhin
> Assignee: Ivan Pavlukhin
> Priority: Major
> Fix For: 2.8
>
>
> For cache with enabled mvcc we should allow running only PESSIMISTIC
> REPEATABLE_READ transactions. For other modes exception should be thrown
> (like is done for SQL API).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
