[
https://issues.apache.org/jira/browse/IGNITE-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857050#comment-15857050
]
Denis Magda commented on IGNITE-4619:
-------------------------------------
[~ptupitsyn],
Here is a couple of comments from my side.
1. Referring to this code
{code}
// When Ignite tx is started manually, it won't be enlisted in TransactionScope.
cache[1] = 0;
using (var tx = transactions.TxStart())
{
using (new TransactionScope())
{
cache[1] = 2;
} // Revert transaction scope: does not affect Ignite tx.
tx.Commit(); // Commit manual tx.
}
cache.Get(1); // returns 2.
{code}
Did you want to say that the value {{cache[1] = 2;}} will be assigned before
the transaction is committed with {{ tx.Commit();}}? Does it mean that
{{cache[1] = 2;}} assignment happens all the time even if you don't call
{{TransactionScope.complete()}}?
2. How do we technically support TransactionScopeOption.Suppress for nested
transactions? I thought that as soon as you start one Ignite transaction using
TransactionScope or Ignite APIs there is no way to put values out of existing
transaction context unless update the cache from a separate Thread.
3. What will be the default transaction isolation level and concurrency mode if
a transaction scope is created with {{new TransactionScope()}} constructor?
Please document this.
4. How can I change the concurrency mode (pessimistic & optimistic)? Please
document this.
The example looks good to me!
> .NET: TransactionScope documentation and example
> ------------------------------------------------
>
> Key: IGNITE-4619
> URL: https://issues.apache.org/jira/browse/IGNITE-4619
> Project: Ignite
> Issue Type: Task
> Components: platforms
> Affects Versions: 1.9
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 1.9
>
>
> Create documentation and example for {{TransactionScope}} support
> (IGNITE-3430).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
