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 2016/12/20 16:37:58 UTC

[jira] [Commented] (ATLAS-1344) Allow types to be created that support parent child hierarchies.

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

Madhan Neethiraj commented on ATLAS-1344:
-----------------------------------------

[~davidrad] with enhancements in ATLAS-1171, org.apache.atlas.typesystem.types.AttributeDefinition.java is replaced by org.apache.atlas.model.typedef.AtlasStructDef.AtlasAttributeDef. AtlasAttributeDef supports the notion of "constraints" - which can used to model parent-child relationships. Currently, "constraints" is used to replace existing fields "isComposite" and "reverseAttributeName" with "foreignKey" and "mappedFromRef" constraints. addons/models/0030-hive_model.json is a good reference for such usage.

Please review and let me know if you have any comments/questions.

> Allow types to be created that support parent child hierarchies.
> ----------------------------------------------------------------
>
>                 Key: ATLAS-1344
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1344
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: David Radley
>            Assignee: David Radley
>
> enhance the Type system to allow entities to be created in parent child hierarchies. 
> I notice that AttributeDefinition currently only support  COLLECTION, SET , OPTIONAL and REQUIRED. There is no collection with a lower bound of 0- which would be required for a parent child type relationship. 
> Also it seems to me that it would be ideal to create an attribute with the guid of the parent / child and then derive the other one from the edge. I may have misunderstood but reverseAttributeName seems to use the name of the attribute not the guid.
> I suggest that iscomposite true and false is supported. 
> When we have this in place, we could use this mechanism for Glossary Categories  
>     
>   



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