atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suma Shivaprasad (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-1690) Introduce top level relationships
Date Fri, 21 Apr 2017 22:10:04 GMT

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

Suma Shivaprasad commented on ATLAS-1690:
-----------------------------------------

A few review comments/questions

1. What does relationship "structure" indicate in the examples? Didnt see any reason why its
needed? Can you pls illustrate why its needed ?
2. Also I saw a note saying we dont need a relationship "name" . However saw that in the examples
and it is needed to define the relation type in the typesystem, correct ?
3. Also if we can illustrate what it means in terms of instances, how would the edges translate
in the graph in the design, that would be good.

> Introduce top level relationships
> ---------------------------------
>
>                 Key: ATLAS-1690
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1690
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: David Radley
>            Assignee: David Radley
>              Labels: VirtualDataConnector
>         Attachments: 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
>
>
> 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
(v6.3.15#6346)

Mime
View raw message