[jira] [Closed] (ASTERIXDB-2006) Exclusive Modify Lock doesn't cover Modify lock

["Abdullah Alamoudi (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ASTERIXDB-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Abdullah Alamoudi closed ASTERIXDB-2006.
----------------------------------------
    Resolution: Fixed

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)