[
https://issues.apache.org/jira/browse/ATLAS-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Le Ma resolved ATLAS-3447.
--------------------------
Resolution: Duplicate
Duplicate Jira with https://issues.apache.org/jira/browse/ATLAS-3491
> Basic Search API does not return child classifications
> ------------------------------------------------------
>
> Key: ATLAS-3447
> URL: https://issues.apache.org/jira/browse/ATLAS-3447
> Project: Atlas
> Issue Type: Bug
> Reporter: Keval Bhatt
> Assignee: Le Ma
> Priority: Major
> Attachments: after deletion - parent.png, before deletion -
> child.png, before deletion - parent.png,
> child_classification_does_not_appear_after_parent_classification_is_reapplied.webm,
>
> childclassification_vanishes_after_parent_classification_association_is_empty.webm
>
>
> Detailed explanation of the issue along with an additional related issue(with
> videos attached).
> Scenario I:
> [^childclassification_vanishes_after_parent_classification_association_is_empty.webm]
> Entity E1 is associated with classification 'Parent' and entity E2 is
> associated with classification 'Child' where 'Child' is subclassification of
> 'Parent'.
> * In the 'Parent' classification details page, E1 and E2 are visible.
> * 'Parent' classification is removed from E1.
> * When we view Parent classification details, E1 no longer appears, but even
> E2 is removed, which is incorrect as the 'Child' is a subclassification of
> 'Parent' and should be visible on the page as the option "Exclude
> subclassifications" is not selected.
>
> Scenario II:
> [^child_classification_does_not_appear_after_parent_classification_is_reapplied.webm]
> After performing steps from scenario I,
> * Reassign 'Parent' classification to E1
> * Navigate to 'Parent' classification details page.
> * E1 is still the only entity visible, even E2 should also be visible as per
> step 1 in Scenario I.
> * Now, remove 'Child' classification from E2 and then reapply 'Child' to E2.
> * Navigate again to 'Parent' classification details page.
> * You will see that now E1 and E2 appear as expected. This seems to be a
> result of a stale connection.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
