atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Radley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-1690) Introduce top level relationships
Date Fri, 01 Sep 2017 08:43:00 GMT

    [ https://issues.apache.org/jira/browse/ATLAS-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150211#comment-16150211
] 

David Radley commented on ATLAS-1690:
-------------------------------------

Hi [~ppadovani]

1) We have not allowed inheritance of relationship types. We felt we can avoid this complication
to Atlas, if we model the types in different ways.    
2) n/a

Interesting use case. some thoughts:
1) Is this GDPR related? In this case, it might be more useful to classify entities as personal
sensitive information and use queries to determine this sort of scope. The advantage of the
query approach is that related objects can be determined at runtime. A principle we used as
 part of the propagation of tags - is that we try to specify a metadata value in one place
and then use rules to propagate. I see the query approach is similar; the customer id could
be defines once in the customer entity and then the associated customer entities determined
by a query.    
   
2) In Atlas currently we only allow one classification of a type against an entity. So if
2 people lived in a house and you view the house address as associated with the person then
this may not work. 

3) Once we have the glossary in place. You will be able to be model your concepts and relationships
in the glossary and map them to the assets. In this case classifications could be applied
to a Glossary term and the relationship between person be defined at a logical level and then
mapped to the assets. For example it might be useful if you were to create aggregation 'owns'
relationships between person and all of the terms you want to associate with it - in this
way could write a very simple query (give me all the owns relationship entities associated
with a customer with a particular id) to get the information you are looking for.    
  
I hope this helps,   all the best David. 




> 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)

Mime
View raw message