[
https://issues.apache.org/jira/browse/IGNITE-12319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16958614#comment-16958614
]
Rajesh commented on IGNITE-12319:
---------------------------------
[~Pavlukhin], I checked the suspend/ resume feature but that would not help the
case I have mentioned above, especially because of its tight coupling and
understanding of suspend/resume in the outer transaction and inner transaction(
started by third party jar) which runs on same node and same thread.
> 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)
