[
https://issues.apache.org/jira/browse/ATLAS-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222083#comment-15222083
]
David Kantor commented on ATLAS-496:
------------------------------------
[~suma.shivaprasad] I was thinking about an optimistic locking mechanism to
prevent stale updates, not a lock to manage concurrency. The idea is that if
two users retrieve the state of some object at time t0, then at t1 user 1 does
a complete update (i.e. a PUT request on the entities resource) of that object,
then at t2 user 2 does a complete update, user 2's update will potentially
overwrite the updates applied by user 1 with stale data, because the object
state being used for user 2's PUT would not include any changes applied by user
1 at t1.
> 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
>
> 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)
