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

Posted to dev@atlas.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/06/24 03:57:00 UTC

[jira] [Commented] (ATLAS-3297) Cache created/updated entities in request context for use in entity-change listeners

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

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

Commit afb67db73038c33e45f398edf2a38e1b5f6e2268 in atlas's branch refs/heads/branch-2.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=afb67db ]

ATLAS-3297: cache added/update entities in request-context, for use in entity-change listeners

(cherry picked from commit 1d2aad52f1053ac03edad78f9568d62010617a97)


> Cache created/updated entities in request context for use in entity-change listeners
> ------------------------------------------------------------------------------------
>
>                 Key: ATLAS-3297
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3297
>             Project: Atlas
>          Issue Type: Improvement
>          Components:  atlas-core
>    Affects Versions: 2.0.0
>            Reporter: Madhan Neethiraj
>            Assignee: Madhan Neethiraj
>            Priority: Major
>             Fix For: 2.1.0, 3.0.0
>
>         Attachments: ATLAS-3297.patch
>
>
> After performing entity create/update operations, Atlas calls change-listeners who handle tasks like create audit logs and send notifications. Change listeners retrieve entities from the store, which could be avoided by caching the entities during create/update phase. This can result in significant improvements in entity create/update operations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)