Mailing-List: contact dev-help@atlas.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@atlas.incubator.apache.org
Date: Wed, 4 Jan 2017 17:10:58 +0000 (UTC)
From: "David Radley (JIRA)" <jira@apache.org>
To: dev@atlas.incubator.apache.org
Message-ID: <JIRA.13024486.1480520323000.640499.1483549858397@Atlassian.JIRA>
In-Reply-To: <JIRA.13024486.1480520323000@Atlassian.JIRA>
References: <JIRA.13024486.1480520323000@Atlassian.JIRA> <JIRA.13024486.1480520323148@arcas>
Subject: [jira] [Commented] (ATLAS-1344) Allow types to be created that
 support parent child hierarchies.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 04 Jan 2017 17:11:02 -0000


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

David Radley commented on ATLAS-1344:
-------------------------------------

[~madhan.neethiraj] I would like to test out these options with SET and LIST, so would appreciate some pointers on how to setup the parent and child custom types (without iscomposite) and create associated entities. I would also like to understand how using the V2 API I could make updates to the SET and LIST attributes, for example alter the order of a LIST or add or remove from the list.   Many thanks ,David.      

> 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)