atlas-dev mailing list archives

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


David Radley commented on ATLAS-1690:

Hi [~suma.shivaprasad],
As always these are great questions. 
3. I will put together a Jira design doc to detail this out. It seems to me that we need the
relationships piece then glossary then the classification piece. As the real power will be
when we can tag a business term and have that propagate through. I think that the propagation
piece sits more naturally in a second access layer around the base entity services. I would
like to concentrate on the relationship implementation, then glossary, then classification.
Do you feel it would be more useful for the community if I were to produce a design doc for
the classification rather than prioritize the relationship implementation      
4. If top level relationship is used to model all relationships - I would agree with you.
This proposal is for the top level relationships to be just for the bidirectional and aggregation
cases; so there is minimal migration impact for existing users of composition relationships.
Are you proposing we model all relationships as a top level relationship object? My suggestion
is to keep the scope down for this initial check in. Then we could more composition into top
level relationships as a follow on piece - if we need to. I think keeping composition relationships
in the entities seems pretty natural.  

> 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