[ https://issues.apache.org/jira/browse/ATLAS-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321811#comment-17321811 ]
ASF subversion and git services commented on ATLAS-3919: -------------------------------------------------------- Commit 0751f16250220271ce63ab7523de37e1f85defda in atlas's branch refs/heads/master from Ashutosh Mestry [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=0751f16 ] ATLAS-3919: Handling classification propagation as deferred-action Co-authored-by: Jayendra Parab <jayendra.pa...@gmail.com> Signed-off-by: Sarath Subramanian <sar...@apache.org> > 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)