[
https://issues.apache.org/jira/browse/IGNITE-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848316#comment-15848316
]
Pavel Tupitsyn edited comment on IGNITE-3430 at 2/1/17 1:05 PM:
----------------------------------------------------------------
Found a problem with calling {{TransactionProxyImpl.prepare()}}: tests hang
sometimes.
Some work to resolve this is being done in IGNITE-3477 for 2.0.
Feature disabled in master, all tests marked with {{[Ignore]}}.
was (Author: ptupitsyn):
Found a problem with calling {{TransactionProxyImpl.prepare()}}: tests hang
sometimes.
Some work to resolve this is being done in IGNITE-3477 for 2.0.
> .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: 1.9
>
>
> 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.15#6346)
