>> This is prefectly valid. Second transaction'll wait for completion of
first.
Alex S., I think you did not get the point. It seems AG meant two jobs of
the same task, so it is one TX. It is unclear to me how to resolve this
automatically. I would agree with AG and permit only primary keys local
Alexey,
Every job is executed in transaction having same semantics as any other
transaction, but transaction is managed by Ignite transparently.
Job's transaction is rolled back on throwing any unchecked exception or
special TransactionRollbackException.
Concurrency issues between jobs are solve
Alexei,
Can you describe the semantics of the task in greater detail?
* What if two jobs on different nodes access and try to put the same key?
(this can be resolved by allowing a job only access local primary keys)
* How do you define the lock acquisition order and prevent deadlocks? I
assume t
