[ 
https://issues.apache.org/jira/browse/ATLAS-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767085#comment-15767085
 ] 

David Radley commented on ATLAS-1186:
-------------------------------------

I have been thinking about the recent discussions around adding terms to the 
glossary and Madhan Neethiraj's helpful comment on Jira ATLAS-1344.  

The Glossary uses the entity V1 API including references to 
AttributeDefinition. A category has a parentid property and an edge to it's 
parent. Children and parents interrogate the edge to and use projections to get 
properties populated. A side effect of this is that we need to delete all the 
edges before we delete a glossary category entity or taxonomy entity.  

The new entity v2 API introduces the ability to have optional multiple 
relationships for atlas structure types. The thought is that maybe this 
mechanism could be used for the category children. It seems to me that we would 
want to change the BaseResourceDefinition to create ClassTypeDefs for the 
Glossary Category Taxonomy and terms. I have raised ATLAS-1410 for this.

If we want one code change per issue - I suggest the following order will make 
the changes easier to manage, consider, and review (and less merging).

- 1186 - with the current design
- 1486 - switch the glossary over to use v2 - simplifying the edge management 
on deletes.
- 1382 - implement terms as entities.  

I could do a bigger single checkin if that is what the reviewers / community 
need.

all the best, David. 

> Add Glossary Category
> ---------------------
>
>                 Key: ATLAS-1186
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1186
>             Project: Atlas
>          Issue Type: New Feature
>    Affects Versions: 0.8-incubating
>            Reporter: David Radley
>            Assignee: David Radley
>              Labels: features
>             Fix For: 0.8-incubating
>
>         Attachments: rb54430(2).patch
>
>
> Add Glossary Category, which would have a name and description and be hung 
> off a taxonomy. The category would contain (composition type) sub categories. 
> Categories can contain terms.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to