[ https://issues.apache.org/jira/browse/ATLAS-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001354#comment-16001354 ]
Madhan Neethiraj commented on ATLAS-1690: ----------------------------------------- bq. Ideally propagation of tags should be defined in Ranger rules - as we are likely to want different tag propagation in different contexts For a consumer to handle tag-propagation, they would need to know of the complex relationship between entities - which might end up having to duplicate much of data in Atlas (and keep them in sync constantly). Let us review few usecases: - when a table/column is classified as PII, any lineage from this table/view/column should also be automatically be classified as PII - when a term is classified as PII, all entities that are associated with the term also should automatically be classified as PII - when a term is classified as PII, all terms that are synonym of this term (and all the entities associated with the synonym terms) also should automatically be classified as PII I think pushing such propagation to the consumers, like Ranger, would require them to understand the complex relationship between various entities. Given such propagations can be handled naturally in a graph DB, it will be cleaner to have this piece owned by Atlas. We can enhance the API for the consumer, to provide 'propagated-tags' along with entities own tags - for example by adding member 'propagatedClassifications' as shown below: {code} public class AtlasEntity { // ... List<AtlasClassification> classifications; List<AtlasPropagatedClassification> propagatedClassifications; } public class AtlasPropagatedClassification { String guidPropagatedFrom; // reference to the entity where the classification was attached to AtlasClassification classification; } {code} CC: [~abhayk] > 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 > > > 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)