atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Madhan Neethiraj (JIRA)" <>
Subject [jira] [Commented] (ATLAS-1690) Introduce top level relationships
Date Mon, 08 May 2017 20:05:04 GMT


Madhan Neethiraj commented on ATLAS-1690:

Ref: [~davidrad]'s earlier comment:
bq. 1. I do not think we should have "to" and "from". This implies a direction.
"to" and "from" may not be appropriate in all relationships. Perhaps we can name it as "endPoint1"
and "endPoint2"?

bq. 2. I am wondering about the use case for a relationship to have more than one type. We
can allow more than one type here if there is a compelling use case.
A single type should be good enough for now. If case for more than one type comes up, we can
review it then.

> 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