atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suma Shivaprasad (JIRA)" <>
Subject [jira] [Commented] (ATLAS-1690) Introduce top level relationships
Date Fri, 05 May 2017 22:30:04 GMT


Suma Shivaprasad commented on ATLAS-1690:

In response to [~davidrad] 's comment , 

4. Yes this is the same as Suma's suggestion of a category; I was thinking of "bidirectional”,
“aggregation” - as association could be directional and contains could be composition
. I will put this in, as we can then put this value into the edge - so we can identify which
edges we need to expand into attributes. Are you OK with these amendments?

--> I think we should have four categories initially - composition, aggregation, bidirectional,
directional. Its important to distinguish between  aggregation and composition I think, since
tag propagation and entity mutation cascade policies like delete etc can be controlled based
on this. Also capturing bidirectional vs directional would help us in migrating the current
technical model where a unidirectional relation could just have ownedRef on one side and there
s no reverseAttribute on the referred end and the default could be bidirectional associations.

> Introduce top level relationships
> ---------------------------------
>                 Key: ATLAS-1690
>                 URL:
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: David Radley
>            Assignee: David Radley
>              Labels: VirtualDataConnector
>         Attachments: Atlas_RelationDef_Json_Structure_v1.pdf, Atlas Relationships proposal
v1.0.pdf, Atlas Relationships proposal v1.1.pdf, Atlas Relationships proposal v1.2.pdf, Atlas
Relationships proposal v1.3.pdf, Atlas Relationships proposal v1.4.pdf, Atlas Relationships
proposal v1.5.pdf, Atlas Relationships proposal v1.6.pdf, Atlas Relationships proposal v1.7.pdf
> Introduce top level relationships including support for 
> -many to many relationships
> - relationship names including the name for both ends and the relationship.

This message was sent by Atlassian JIRA

View raw message