[
https://issues.apache.org/jira/browse/ATLAS-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007404#comment-16007404
]
Madhan Neethiraj commented on ATLAS-1690:
-----------------------------------------
>From [~davidrad]:
bq. I think the propagated classifications would be derived at query time and
could be useful -do we need an effective classification?
I am not suggesting to materialize (i.e. copy) the propagated tags - that will
add unnecessary complexity in dealing with tag attribute value changes,
relationship changes, etc. Deriving the propagated tags dynamically when
looking at (or retreiving) entity details would be a good choice.
bq. do we need an effective classification?
I think what is the "effective classification" is better left to the consumer
of the tags of an entity. The requirement might vary, depending on how the tags
are used. The example you detailed is one use case: to use of classification
"level" to determine the effective classification. There could be other ways to
pick the effective classification.
>From Atlas API perspective, I think we should make it clear which tags are
>directly associated with the entity being retrieved and which ones come via
>propagation.
bq. I wonder whether a smarter approach would be to tag the relationship as
"propagate-1-to-2" (hopefully something more meaningful like
propogate-table-to-column") and Ranger picks up this hint. Ranger could decide
to run a simple rule of propagating all the tags from 1 to 2 or a more complex
rule taking other conditions into account.
Wouldn't this require Ranger to know about all the entities, relationships and
the propagation rules in Atlas? And a way to navigate them easily? This might
be easier in Atlas, give we use Graph DB; but for consumer's of Atlas
entity/tags, it might not be practical. Also, I think it will be good to see
both tags and propagated-tags in Atlas UI - which would require Atlas to deal
with propagation logic. Given this, I think it will be useful to make this
information available via Atlas API.
> 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)
