[
https://issues.apache.org/jira/browse/ATLAS-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598463#comment-16598463
]
Graham Wallis commented on ATLAS-2853:
--------------------------------------
In addition to the problem of what happens on a rollback, the problem also
affects commit - but I think your patch addresses it. The additional aspect to
the problem is that if the notification is sent prior to commit then the
subscribers can pick it up and query the graph before the graph has had a
chance to commit - so the subscribers see the old (stale) state. The most
obvious example of this was on an entity create - the subscriber then queried
the graph and the graph denied any knowledge of the new entity. Doing the
commit before send is better in both the commit and rollback cases.
> Entity notifications to be sent after transaction commit
> --------------------------------------------------------
>
> Key: ATLAS-2853
> URL: https://issues.apache.org/jira/browse/ATLAS-2853
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Priority: Critical
> Fix For: 0.8.3, 1.1.0, 2.0.0
>
> Attachments: ATLAS-2853.patch
>
>
> Currently, notification on entity changes (create/update/delete entities,
> add/update/remove classifications on entities) are sent before the changes
> are committed in the database. If commit fails, the entity state seen by
> notification receivers would be different from Atlas. To avoid this, Atlas
> server should entity notifications only after the transaction is committed to
> the database.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
