You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by Guru Stron <gu...@gmail.com> on 2020/07/05 13:52:38 UTC

.NET different behavior when using TransactionScope and ITransactions.Start

Dear Igniters,

It seems that .NET client behaves differently when TransactionScope is used
for transactions compared to "native" transactions. I've opened  a bug
<https://issues.apache.org/jira/browse/IGNITE-13214> can somebody take a
look and verify that it is one?

Thanks in advance.

Re: .NET different behavior when using TransactionScope and ITransactions.Start

Posted by Pavel Tupitsyn <pt...@apache.org>.

Guru Stron,

Good catch, this is indeed a bug - we don't handle ambient transactions
in cache read operations, and this is a mistake.

I'll make sure this is fixed for 2.9.
Thanks!

On Sun, Jul 5, 2020 at 4:52 PM Guru Stron <gu...@gmail.com> wrote:

> Dear Igniters,
>
> It seems that .NET client behaves differently when TransactionScope is used
> for transactions compared to "native" transactions. I've opened  a bug
> <https://issues.apache.org/jira/browse/IGNITE-13214> can somebody take a
> look and verify that it is one?
>
> Thanks in advance.
>