[
https://issues.apache.org/jira/browse/IGNITE-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450434#comment-16450434
]
Ivan Daschinskiy commented on IGNITE-8075:
------------------------------------------
[~ptupitsyn]
>>> _Also, assertion in registerTx will fail if we call
>>> GetLocalActiveTransactions twice._
I suppose that won't. registerTx autoicrement atomic counter TX_ID_GEN. It
should not fail with assertion.
>>>>_the big problem here is that we call registerTx in Java, which means that
>>>>user has to manually Dispose every returned transaction_
Yes, I agree. But the same is for ordinary transaction, isn't it?
> .NET: setRollbackOnTopologyChangeTimeout, withLabel, localActiveTransactions,
> setTxTimeoutOnPartitionMapExchange
> ----------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-8075
> URL: https://issues.apache.org/jira/browse/IGNITE-8075
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 2.4
> Reporter: Alexei Scherbakov
> Assignee: Ivan Daschinskiy
> Priority: Major
> Fix For: 2.6
>
>
> Neet to add new methods as part of .NET API:
> org.apache.ignite.configuration.TransactionConfiguration#txTimeoutOnPartitionMapExchange
> - timeout for automatic rollback on exchange.
> org.apache.ignite.IgniteTransactions#withLabel - tx label
> org.apache.ignite.IgniteTransactions#localActiveTransactions - list of local
> active transactions.
> org.apache.ignite.IgniteCluster#setTxTimeoutOnPartitionMapExchange
> Java implementation is currently available at a branch [1]
> [1] https://github.com/gridgain/apache-ignite/tree/ignite-6827-2
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
