ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3430) .NET: Run Ignite transactions via standard TransactionScope API
Date Thu, 02 Feb 2017 09:39:51 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849720#comment-15849720
] 

Pavel Tupitsyn commented on IGNITE-3430:
----------------------------------------

Java has {{TransactionConfiguration.UseJtaSynchronization}} property (false by default).
When false, {{prepare}} is never called from {{CacheJtaResource}}. We could add the same option
in .NET, but I'm not sure if this really provides any benefits.

> .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
>
>         Attachments: threads_report.txt
>
>
> 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)

Mime
View raw message