Re: Ignite Transaction with Locks but not SERIALIZABLE user case.

2017-10-31 Thread afedotov
Hello, increment/decrement is a read-modify-write operation, so to achieve the desired behavior you need to lock the key and perform the operation under that lock. So you need to use a transaction mode and isolation level that meet the requirements. For this case, you could use the approach

Ignite Transaction with Locks but not SERIALIZABLE user case.

2017-10-30 Thread bingili
Hello, I have some operations which does not care about the order, e.g., each operation is to increase the key value by 1 or decrease by 1. So I need a lock to protect each key on read and write. Also I need to put operations in transaction, since ignite will handle the commit and rollback.