atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <>
Subject [jira] [Commented] (ATLAS-3919) Handling classification propagation as deferred-action
Date Wed, 14 Apr 2021 23:51:00 GMT


ASF subversion and git services commented on ATLAS-3919:

Commit 6eb970ce23d4ce290687512d3871db8f086a9e4f in atlas's branch refs/heads/branch-2.0 from
Ashutosh Mestry
[;h=6eb970c ]

ATLAS-3919: Handling classification propagation as deferred-action

Co-authored-by: Jayendra Parab <>

Signed-off-by: Sarath Subramanian <>
(cherry picked from commit 0751f16250220271ce63ab7523de37e1f85defda)

> Handling classification propagation as deferred-action
> ------------------------------------------------------
>                 Key: ATLAS-3919
>                 URL:
>             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

This message was sent by Atlassian Jira

View raw message