[
https://issues.apache.org/jira/browse/IGNITE-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15785286#comment-15785286
]
Pavel Tupitsyn commented on IGNITE-3430:
----------------------------------------
If Ignite transaction is already started when we encounter a transactional
operation within {{TransactionScope}}, then we should NOT enlist it in ambient
transaction. It means that user manages Ignite transactions manually.
This feature changes existing behavior and may break existing Ignite.NET
applications (which use {{TransactionScope}} for other purposes), therefore
this should be merged to {{ignite-2.0}} branch.
> .NET: Run Ignite transactions via standard TransactionScope API
> ---------------------------------------------------------------
>
> Key: IGNITE-3430
> URL: https://issues.apache.org/jira/browse/IGNITE-3430
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
> Affects Versions: 1.6
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .net, roadmap
> Fix For: 2.0
>
>
> Automatically enlist Ignite operations in current transaction scope when
> applicable (when cache is transactional).
> https://msdn.microsoft.com/en-us/library/system.transactions.transactionscope(v=vs.110).aspx
> https://msdn.microsoft.com/en-us/library/ee818754(v=vs.110).aspx
> This boils down to implementing {{IEnlistmentNotification}} and calling
> {{Transaction.Current.Enlist}} when doing transactional operations.
> Later we may want to implement {{ISinglePhaseNotification}} which is an
> optimization.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
