You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Madhan Neethiraj (JIRA)" <ji...@apache.org> on 2018/05/16 05:14:00 UTC

[jira] [Resolved] (ATLAS-2679) [Glossary] Derive category's qualifiedName using hierarchy

     [ https://issues.apache.org/jira/browse/ATLAS-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Madhan Neethiraj resolved ATLAS-2679.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0

Committed to following branches:
 - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/66f8ae16
 - branch-1.0: http://git-wip-us.apache.org/repos/asf/atlas/commit/65e3a114

> [Glossary] Derive category's qualifiedName using hierarchy
> ----------------------------------------------------------
>
>                 Key: ATLAS-2679
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2679
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Apoorv Naik
>            Assignee: Apoorv Naik
>            Priority: Major
>             Fix For: 1.0.0
>
>
> Currently the qualifiedName is derived using displayName and Glossary's qualifiedName.
>  
> In this patch, the qualifiedName is derived from it's Hierarchy and any changes in the hierarchy itself will trigger a cascaded update of all children.
>  
> E.g. Cat1 is parent category, Cat2 is child category
>  
> Derived qualfiedName of Cat2 = Cat2.Cat1@<glossaryQualifiedName>
>  
> The following actions trigger a cascaded update of the children categories
>  
>  # Change of anchor
>  # Change of Parent
>  # Removal of children from a parent (similar to #2)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)