[
https://issues.apache.org/jira/browse/ATLAS-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461566#comment-16461566
]
Sarath Subramanian commented on ATLAS-2638:
-------------------------------------------
When updating classifications propagate flag (true/false), finding
propagated-to entities should look for blocked classification restriction also.
Fixed it in patch.
> Disabling tag propagation at an edge : Switching propagate flag after adding
> tag to blockedPropagatedClassifications
> --------------------------------------------------------------------------------------------------------------------
>
> Key: ATLAS-2638
> URL: https://issues.apache.org/jira/browse/ATLAS-2638
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 1.0.0
> Reporter: Sarath Subramanian
> Assignee: Sarath Subramanian
> Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2638.1.patch
>
>
> 1. Created a database db1 and table db1.table1.
> 2. Updated the relationship between db1 and table1 to TWO_TO_ONE.
> 3.Added tag1 to db1. Tag is propagated to table1.
> 4. Updated relationship between db1 and table1 and added tag1 to
> blockedPropagatedClassifications.
> 5. now , tag1 is removed from table1.
> 6. Now switched propagate flag value of tag1 at db1 from True to False.
> 7. In relationship definition between db1 and table1 , tag1 is removed from
> blockedPropagatedClassifications.
> 8. Now switched propagate flag value of tag1 at db1 from False to True.
> 9. In relationship definition between db1 and table1 , tag1 is added back
> automatically to blockedPropagatedClassifications.
> 10. Now, though tag1 is in blockedPropagatedClassifications , tag1 is still
> propagated to table1.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
