u please let me know what is the expected release in which
> this fix will be included?
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Error-on-Transactions-with-Write-Behind-tp4736p4817.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hey, It does work with READ_COMMITTED
However, can you please let me know what is the expected release in which
this fix will be included?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Error-on-Transactions-with-Write-Behind-tp4736p4817.html
Sent from the
k won't be acquired on the 'get' operation as in case
> 2.
>
> --
> Denis
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Error-on-Transactions-with-Write-Behind-tp4736p4764.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
operation as in case
2.
--
Denis
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Error-on-Transactions-with-Write-Behind-tp4736p4764.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
data, where as the second one is used for writing to the database
asynchronously ).
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Error-on-Transactions-with-Write-Behind-tp4736p4749.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
abble.com/Error-on-Transactions-with-Write-Behind-tp4736p4747.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
with different write-behind setting can't be
enlisted in one transaction)
Have you got any work arounds for this?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Error-on-Transactions-with-Write-Behind-tp4736.html
Sent from the Apache Ignite Users mailing