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

Posted to user@ignite.apache.org by VeenaMithare <v....@cmcmarkets.com> on 2020/02/18 23:24:38 UTC

Transaction Ids associated with Cache Put (Atomicity mode TRANSACTIONAL)

I am also noticing when I do insert from the dbeaver( jdbc thin client )
the transaction id associated with the TX_STARTED/TX_COMMITTED event is
different from the xid parameter sent with the  Cache_PUT event . 

Why is this so ? 

Should the both not be the same ?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/