[
https://issues.apache.org/jira/browse/ATLAS-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321813#comment-17321813
]
ASF subversion and git services commented on ATLAS-3919:
--------------------------------------------------------
Commit 6eb970ce23d4ce290687512d3871db8f086a9e4f in atlas's branch
refs/heads/branch-2.0 from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=6eb970c ]
ATLAS-3919: Handling classification propagation as deferred-action
Co-authored-by: Jayendra Parab <[email protected]>
Signed-off-by: Sarath Subramanian <[email protected]>
(cherry picked from commit 0751f16250220271ce63ab7523de37e1f85defda)
> Handling classification propagation as deferred-action
> ------------------------------------------------------
>
> Key: ATLAS-3919
> URL: https://issues.apache.org/jira/browse/ATLAS-3919
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
> Affects Versions: 2.0.0, 2.1.0
> Reporter: Jayendra Parab
> Assignee: Jayendra Parab
> Priority: Major
>
> Currently, whenever a user assigns a tag or updates a tag on an entity, it
> gets propagated to all the entities derived from the tagged entity. This
> operation takes quite a lot of time to complete (sometimes into minutes) and
> causes usability issues on the UI and other clients invoking the REST API
> To resolve this issue, tag-propagation needs to be handled as
> deferred-action, so that time consuming like propagation, audits &
> notifications can be processed in background threads
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
