[
https://issues.apache.org/jira/browse/IGNITE-12319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957768#comment-16957768
]
Ivan Pavlukhin commented on IGNITE-12319:
-----------------------------------------
[~rajeshn], yep, there is a difference. I thought about _nested_ transactions
as described in
[Spring|https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/transaction/annotation/Propagation.html].
Will {{org.apache.ignite.transactions.Transaction.suspend/resume}} do the
trick? Pay attention that _pessimistic_ transaction support was not released
yet (targeted to 2.8) IGNITE-5714
> Nested Transaction support in Ignite
> ------------------------------------
>
> Key: IGNITE-12319
> URL: https://issues.apache.org/jira/browse/IGNITE-12319
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.7.6
> Reporter: Rajesh
> Priority: Major
>
> There is no support for Nested transaction. For example, if there is an outer
> transaction which works on few caches and within that there is a transaction
> which is opened by a third party client to update their caches then it throws
> exception as current thread already has the transaction.
> This scenario is encountered multiple times where the inner transaction needs
> to be committed on success of inner transaction even if the outer transaction
> fails.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
