[
https://issues.apache.org/jira/browse/ATLAS-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17001297#comment-17001297
]
ASF subversion and git services commented on ATLAS-3568:
--------------------------------------------------------
Commit ec70a669782e59457ed50b13e92497386d4e9a1c in atlas's branch
refs/heads/branch-2.0 from Saqeeb Shaikh
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ec70a66 ]
ATLAS-3568: Performance improvements in writing audit logs #2
Signed-off-by: Sarath Subramanian <[email protected]>
(cherry picked from commit f5dcc7b7036414f3e382d172dbe10ed83be90bda)
> 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)
