Re: Explicit lock whithin a transaction

2016-11-20 Thread akaptsan
Would you please evaluate another variant: use READ_COMMITTED mode and invoke an EntryProcessor to acquire explicit lock -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Explicit-lock-whithin-a-transaction-tp8586p9106.html Sent from the Apache Ignite Users

Re: Explicit lock whithin a transaction

2016-11-19 Thread vkulichenko
-users.70518.x6.nabble.com/Explicit-lock-whithin-a-transaction-tp8586p9104.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Explicit lock whithin a transaction

2016-11-19 Thread akaptsan
.x6.nabble.com/Explicit-lock-whithin-a-transaction-tp8586p9102.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Explicit lock whithin a transaction

2016-11-18 Thread vkulichenko
s.70518.x6.nabble.com/Explicit-lock-whithin-a-transaction-tp8586p9089.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Explicit lock whithin a transaction

2016-11-18 Thread akaptsan
of them must be locked -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Explicit-lock-whithin-a-transaction-tp8586p9069.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Explicit lock whithin a transaction

2016-11-17 Thread vkulichenko
.nabble.com/Explicit-lock-whithin-a-transaction-tp8586p9061.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Explicit lock whithin a transaction

2016-11-17 Thread akaptsan
objects I need to read until I come to certain point within transaction. In SQL I have following options: - read without lock - select ... - read and lock - select ... for update -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Explicit-lock-whithin-a-transaction

Re: Explicit lock whithin a transaction

2016-11-17 Thread akaptsan
PESSIMISTIC-READ_COMMITTED locks ALL objects I read in transaction. It's overkill I need to readAndLock for some objects and readWithoutLock for others -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Explicit-lock-whithin-a-transaction-tp8586p9054.html Sent

Re: Explicit lock whithin a transaction

2016-11-17 Thread vdpyatkov
/Explicit-lock-whithin-a-transaction-tp8586p8593.html -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Explicit-lock-whithin-a-transaction-tp8586p9051.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Explicit lock whithin a transaction

2016-11-01 Thread akaptsan
May be I should use empty EntryProcessor for this? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Explicit-lock-whithin-a-transaction-tp8586p8647.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Explicit lock whithin a transaction

2016-10-29 Thread akaptsan
We don't need lock ALL entries on read, only SOME of them. Typically we need lock objects which will be modified latter in the transactions but we don't want lock all read-only objects -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Explicit-lock-whithin

Re: Explicit lock whithin a transaction

2016-10-28 Thread vkulichenko
Hi, You should use PESSIMISTIC, REPEATABLE_READ transaction in this case. It will lock the entry on read. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Explicit-lock-whithin-a-transaction-tp8586p8593.html Sent from the Apache Ignite Users mailing list

Explicit lock whithin a transaction

2016-10-28 Thread akaptsan
it by: select * from table where id=? *FOR UPDATE* How can I do something similar with Ignite? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Explicit-lock-whithin-a-transaction-tp8586.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.