[ https://issues.apache.org/jira/browse/KUDU-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17307372#comment-17307372 ]
ASF subversion and git services commented on KUDU-2612: ------------------------------------------------------- Commit 6983d25c35df8569c1851bf27e2c75e98036c10d in kudu's branch refs/heads/master from Hao Hao [ https://gitbox.apache.org/repos/asf?p=kudu.git;h=6983d25 ] KUDU-2612: add ScopedPartitionLock This patch introduces a coarse-grained partition-level lock ScopedPartitionLock to prevent dirty writes for multi-row transactions, similar to the ScopedRowLock, but for locking the entire LockManager instead of individual rows. A partition lock can only be held by a single transaction at a time. A given transaction can acquire the lock multiple times. To prevent deadlocks, a wait-die scheme is used -- if a transaction requires a lock held by another transaction: 1. Retry the op if the requesting transaction has a lower txn ID than the current holder ("wait"), 2. Otherwise abort the requesting transaction immediately ("die"). A later patch will plumb this locking into participant ops and transactional write ops. Change-Id: I158115739ce3e7cfb77bbcb854e834336c1256b1 Reviewed-on: http://gerrit.cloudera.org:8080/17097 Reviewed-by: Alexey Serbin <aser...@cloudera.com> Tested-by: Andrew Wong <aw...@cloudera.com> > Implement multi-row transactions > -------------------------------- > > Key: KUDU-2612 > URL: https://issues.apache.org/jira/browse/KUDU-2612 > Project: Kudu > Issue Type: Task > Reporter: Mike Percy > Priority: Major > Labels: roadmap-candidate > > Tracking Jira to implement multi-row / multi-table transactions in Kudu. -- This message was sent by Atlassian Jira (v8.3.4#803005)