atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-2853) Entity notifications to be sent after transaction commit
Date Fri, 31 Aug 2018 16:48:00 GMT

    [ https://issues.apache.org/jira/browse/ATLAS-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598999#comment-16598999
] 

ASF subversion and git services commented on ATLAS-2853:
--------------------------------------------------------

Commit e576b763a21ae3089e80a1448aaef9e9a678fcb8 in atlas's branch refs/heads/branch-1.0 from
[~madhan@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=e576b76 ]

ATLAS-2853: updated to send entity-notifications after successful graph transaction commit

(cherry picked from commit 56eefb2a9806265df997dda2ef70274eede72675)


> 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)

Mime
View raw message