You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Sarath Subramanian (Jira)" <ji...@apache.org> on 2019/12/20 17:33:00 UTC

[jira] [Commented] (ATLAS-3568) Performance improvements in writing audit logs

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

Sarath Subramanian commented on ATLAS-3568:
-------------------------------------------

attaching patch from [~saqeeb.s]

> Performance improvements in writing audit logs
> ----------------------------------------------
>
>                 Key: ATLAS-3568
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3568
>             Project: Atlas
>          Issue Type: Improvement
>          Components:  atlas-core
>    Affects Versions: 2.0.0
>            Reporter: Saqeeb Shaikh
>            Assignee: Saqeeb Shaikh
>            Priority: Major
>         Attachments: ATLAS-3568.001.patch
>
>
> Atlas server generates audit logs on changes to entities - like add/remove classifications, entity attribute updates, etc. Add/remove of classifications to an entity can result in multiple entities to be updated due to tag-propagation. In such cases, the time taken to create audit logs can be reduced by writing audits for all updated entities in one call to the audit store, instead of current implementation that writes audit logs for one entity at a time.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)