[
https://issues.apache.org/jira/browse/ASTERIXDB-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16105748#comment-16105748
]
ASF subversion and git services commented on ASTERIXDB-2006:
------------------------------------------------------------
Commit b5d4f56ae427351a282af4c8d740d8b91d21f80f in asterixdb's branch
refs/heads/master from [~alamoudi]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=b5d4f56 ]
[ASTERIXDB-2006][TX] Fix metadata lock containment rules
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
- Locks with mode exclusive modify cover all modify modes
Change-Id: Ib0ecbaed86370707d560b7d0c3e6933c198aab41
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1907
Sonar-Qube: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
BAD: Jenkins <[email protected]>
Reviewed-by: Till Westmann <[email protected]>
Integration-Tests: Jenkins <[email protected]>
> Exclusive Modify Lock doesn't cover Modify lock
> -----------------------------------------------
>
> Key: ASTERIXDB-2006
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2006
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: TX - Transactions
> Reporter: Abdullah Alamoudi
> Assignee: Abdullah Alamoudi
>
> When acquiring a metadata lock, the caller passes the requested mode. For
> example READ and WRITE.
> When the lock has already been acquired, the lock manager checks if the
> acquired mode covers the requested mode. For example, WRITE covers READ but
> not the other way around.
> EXCLUSIVE_MODIFY_LOCK covers MODIFY lock as well but that was not implemented
> correctly in the metadata lock manager.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
