[
https://issues.apache.org/jira/browse/ATLAS-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18005507#comment-18005507
]
chaitali borole edited comment on ATLAS-4889 at 7/15/25 6:24 AM:
-----------------------------------------------------------------
(Scenario 1 and Scenario 2 usecases are written in same image)
Scenario 1:
Where there are simply 4 entities in ctas
If ctas1 is targeted then it has *classi1,classi2,classi3 *propagated and it
will traverse and fetch till firstparent as it is parent of classi1
,secondParent as it is parent of classi2 , thirdparent as it is parent of
classi3
Irrespective of this if this a scenario if ctas1entity has only 1
classification propagated i.e classi1
it will still fetch all entities till firstParent as parent of classi1
Scenario2:
if CT5 is targeted and has c1,c2,c3 classifications propagated
in the image we can see T3 has blocked c1 and c2 from edge connecting CT1
T3 has blocked C3 classification on edge connecting CT2 hence in such
situations to catch both the lineage is required hence it will fetch incoming
edges till corresponding parent of classifications
Scenario3:
If CT7 is targeted entity then it has classi2 propagated and so it will
traverse till CT1 as it is parent of classi2
While traversing it will find CT1 has another classification propagated classi1
which was blocked for further propagation in such case it will again traverse
till T1 as it is parent of classi1.
was (Author: chaitali):
!IMG_9139.jpeg!
Scenario 1:
Where there are simply 4 entities in ctas
If ctas1 is targeted then it has *classi1,classi2,classi3 *propagated and it
will traverse and fetch till firstparent as it is parent of classi1
,secondParent as it is parent of classi2 , thirdparent as it is parent of
classi3
Irrespective of this if this a scenario if ctas1entity has only 1
classification propagated i.e classi1
it will still fetch all entities till firstParent as parent of classi1
Scenario2:
if CT5 is targeted and has c1,c2,c3 classifications propagated
in the image we can see T3 has blocked c1 and c2 from edge connecting CT1
T3 has blocked C3 classification on edge connecting CT2 hence in such
situations to catch both the lineage is required hence it will fetch incoming
edges till corresponding parent of classifications
!IMG_9138.jpeg!
If CT7 is targeted entity then it has classi2 propagated and so it will
traverse till CT1 as it is parent of classi2
While traversing it will find CT1 has another classification propagated classi1
which was blocked for further propagation in such case it will again traverse
till T1 as it is parent of classi1.
> Incremental export : When an entity has tag propagated and is exported , the
> tag is not propagated to it in the export.
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: ATLAS-4889
> URL: https://issues.apache.org/jira/browse/ATLAS-4889
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
> Affects Versions: 3.0.0
> Reporter: chaitali borole
> Assignee: chaitali borole
> Priority: Major
> Attachments: IMG_9138.jpeg, IMG_9139.jpeg
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> STEPS TO REPRODUCE:
> Create table1
> Create lineage CTAS tables of depth 10 ( t1 -> t2 -> t3 ..... t10)
> Associate tag tag1 to table1
> Export table table10
> Import the zip
> CURRENT BEHAVIOUR:
> table10 doesn't have the tag associated to the it since the "entityGUID" is
> of table1's and table1 is not exported
>
> EXPECTED BEHAVIOUR:
> table10 should have tag1 exported
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
