[
https://issues.apache.org/jira/browse/ATLAS-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Radley updated ATLAS-1690:
--------------------------------
Attachment: Atlas Relationships proposal v1.9.pdf
We had a meeting yesterday with various companies participating to talk about
the implementation / design of Jira on top level relationships. We reached
consensus that we wanted to include composition relationships as well as
association and aggregation relationships.
We also talked about tag propagation, suggesting it would be useful to have an
enumeration defined in the RelationshipDef indicating that which way tags
should flow. Thinking about this I wonder if this is too blunt an instrument.
For example if I define a has-a relationship in the RelationshipDef - then we
do not want to always propagate all tags in all circumstances . - we may
sometimes want to propagate some tags but not others.
I have updated the design document to make it more coherent and added a
proposal to extend the endpoint in the relationshipDef to include a
tags-to-propagate list of ClassificationDef names, these would be the
classifications that would be propagated from the entity of that type across
the relationship at runtime.
> 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_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, Atlas
> Relationships proposal v1.8.pdf, Atlas Relationships proposal v1.9.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)
