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 Thu, 11 May 2017 23:51:04 GMT


Madhan Neethiraj commented on ATLAS-1690:

On earlier comment from [~cmgrote]:

bq. What about "propagatesTags" being an enum rather than a simple boolean, e.g. "FROM-TO",
"TO-FROM", "BI-DIRECTIONAL"; in case there are scenarios where it would make sense to apply
the super-set of tags (from both sides of the relationship)?
Yes. This is a good idea and will be very helpful. For example, in case of synonym relationship
between terms, tags associated with either end of the relationship might be applicable to
terms at each end. I think one of the enum value should be "NONE" - to handle the cases where
tags shouldn't be propagated.

> 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