ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Popov <tank2.a...@gmail.com>
Subject Re: Locking rows within Ignite Transactions
Date Mon, 04 Dec 2017 14:35:05 GMT

Please note that cache.get(N) does not lock all "rows" inside a transaction.
It just locks "row" with N key.

Actually, you should not lock data that is not involved in the transaction.
That is why the explicit lock is prohibited. It should be done out of
transaction scope.

If your case requires some specific lock inside transaction scope you can
use cache.get(). If you Cache entry (i.e. "row") is huge and you don't need
all the data, you can reduce some overhead by returning binary
(unmarshalled) data via cache.withKeepBinary().get().

Thank you,


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

View raw message