[jira] [Commented] (ATLAS-1690) Introduce top level relationships
[ https://issues.apache.org/jira/browse/ATLAS-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181262#comment-16181262 ] Pierre Padovani commented on ATLAS-1690: [~davidrad] I create this issue, as it seems to be the one common behavior that seems to be affecting this feature: https://issues.apache.org/jira/browse/ATLAS-2178 > 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.10.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.4.14#64029)
[jira] [Commented] (ATLAS-1690) Introduce top level relationships
[ https://issues.apache.org/jira/browse/ATLAS-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180979#comment-16180979 ] David Radley commented on ATLAS-1690: - [~ppadovani] In the master branch, we have added the new RelationshipDefs,[~sarath.ku...@gmail.com] has added support for relationship instances, there is an active Jira adding update and delete support. There is an ongoing Jira relating to the implementation of relationship tagPropagation. Some work has been done to add tagPropagation to the existing Hadoop models, using relationshipDef type definitions; this is a way to get tag propagation with the legacy reference attributes. You need to move to the new cleaner relationships to get aggregation and many to many support. I am not aware of any enhancements in the lineage area regarding relationships - I suggest you raise all the issues that you see as Jiras and we will have a look at them. Please raise as Jiras any issues/ regressions that you are seeing as 'a bit unstable', so we can fix them. > 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.10.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.4.14#64029)
[jira] [Commented] (ATLAS-1690) Introduce top level relationships
[ https://issues.apache.org/jira/browse/ATLAS-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180893#comment-16180893 ] Pierre Padovani commented on ATLAS-1690: [~davidrad] Thanks for the explanation. What is the status of this work? I've tried using 0.9 and have found the new relationship system to be a bit unstable in regards to the legacy compatibility. I've also noticed that the existing lineage API does not function correctly in conjunction with an implementation that uses relationship defs. The exact same model without defined relationship defs, functions correctly in 0.8.1. Thanks! Pierre > 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.10.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.4.14#64029)
[jira] [Commented] (ATLAS-1690) Introduce top level relationships
[ https://issues.apache.org/jira/browse/ATLAS-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149536#comment-16149536 ] Pierre Padovani commented on ATLAS-1690: Two questions on this work: 1) Can a RelationshipType inherit from another RelationshipType? 2) If yes for #1, how does that affect tag propagation? My use case: Given a set of metadata that belongs to a particular customer, where we use a classification with an attribute that contains the customer id, we would want that classification to propagate to all related entities. If we had a relationship type that was generic in nature and specified that the classification for the customer propagated, it would be nice to be able to specify sub-types that provide additional behaviors. > 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.10.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.4.14#64029)
