You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@atlas.apache.org by "David Kantor (JIRA)" <ji...@apache.org> on 2016/04/07 20:36:25 UTC

[jira] [Assigned] (ATLAS-496) Optimistic locking to prevent update conflicts

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

David Kantor reassigned ATLAS-496:
----------------------------------

    Assignee: David Kantor

> Optimistic locking to prevent update conflicts
> ----------------------------------------------
>
>                 Key: ATLAS-496
>                 URL: https://issues.apache.org/jira/browse/ATLAS-496
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: David Kantor
>            Assignee: David Kantor
>
> The ATLAS api does not adequately protect against concurrent activity against the same entity, type or other object.
> Some form of locking is desirable, though strict locking and/or 2pc are problematic in a highly distributed environment. Optimistic locking may be the best approach so that at a minimum an application attempting to do a modification will be alerted if another application has touched the same (object) since that app last retrieved the object.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)