You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/04/30 05:01:00 UTC
[jira] [Commented] (ATLAS-4269) Deferred Actions : When a tag is
propagated from an entity via 2 processes , blocking 1 process removes tag
propagated from another process
[ https://issues.apache.org/jira/browse/ATLAS-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337071#comment-17337071 ]
ASF subversion and git services commented on ATLAS-4269:
--------------------------------------------------------
Commit 85e3c5cf64747432bd434bbf1573224988c37bf6 in atlas's branch refs/heads/master from Sarath Subramanian
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=85e3c5c ]
ATLAS-4269: Deferred Actions : When a tag is propagated from an entity via 2 processes , blocking 1 process removes tag propagated from another process
> Deferred Actions : When a tag is propagated from an entity via 2 processes , blocking 1 process removes tag propagated from another process
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ATLAS-4269
> URL: https://issues.apache.org/jira/browse/ATLAS-4269
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 2.1.0
> Reporter: Sarath Subramanian
> Assignee: Sarath Subramanian
> Priority: Major
> Labels: tagpropagation
> Fix For: 3.0.0, 2.2.0
>
> Attachments: default.t4@cm.png
>
>
> 1.Create a lineage as attached in the screenshot (i.e) tag propagated from a source using 2 processes to a target
> 2. Add a tag to t3 , now the tag is propagated to t4 via both process1 and process2.
> 3. Now block the propagation from t3 to process1.
> 4. Expectation is that , tag will be propagated via process2 to t4. But the propagated tag is removed from t4
> !default.t4@cm.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)