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 2020/08/12 20:18:00 UTC

[jira] [Updated] (ATLAS-3919) Handling classification propagation as deferred-action

     [ https://issues.apache.org/jira/browse/ATLAS-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sarath Subramanian updated ATLAS-3919:
--------------------------------------
    Affects Version/s: 2.0.0
                       2.1.0

> 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)