[
https://issues.apache.org/jira/browse/IGNITE-7369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160465#comment-17160465
]
Pavel Tupitsyn commented on IGNITE-7369:
----------------------------------------
[~GuruStron] I've did another review pass, looks like we are in a good shape!
Please add a test for connection failure use case - what happens? Can the user
catch the exception and continue the work somehow?
> .NET: Thin client: Transactions
> -------------------------------
>
> Key: IGNITE-7369
> URL: https://issues.apache.org/jira/browse/IGNITE-7369
> Project: Ignite
> Issue Type: Improvement
> Components: platforms, thin client
> Affects Versions: 2.4
> Reporter: Pavel Tupitsyn
> Assignee: Sergey Stronchinskiy
> Priority: Major
> Labels: .NET, iep-34
> Fix For: 2.9
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Implement transactions in thin client protocol and .NET thin client.
> Main issue: Ignite transactions are tied to a specific thread.
> See how JDBC works around this by starting a dedicated thread.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
