[
https://issues.apache.org/jira/browse/ATLAS-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369846#comment-16369846
]
David Radley commented on ATLAS-2456:
-------------------------------------
[[email protected]] Thanks for your reply.
>From your responses, is it true that:
* many propagated classifications of the same type can exist for an entity
* a propagated classification can exist with the same type as an explicitly
defined classification
* on point 7 - does this mean that only one classification type or any of its
sub types can be applied to an entity
I suggest:
* we do not propagate a classification of a given type to an entity if there
is already a classification of that type defined (we should account for sub
types here)
* we should not allow more than one classification of a given type against an
entity across explicitly defined classification and propagated classifications.
This means that a policy only has to consider one classification and its
ramifications. I am not sure how we resolve the potential conflicts; ideally
this would be resolved using some rules and a data steward. If we could search
for these conflicts (maybe with a new conflicted status on the entity) , then a
classification could be then explicitly defined on the entity and would force
which classification values were effective.
> Implement tag propagation using relationships
> ---------------------------------------------
>
> Key: ATLAS-2456
> URL: https://issues.apache.org/jira/browse/ATLAS-2456
> Project: Atlas
> Issue Type: New Feature
> Components: atlas-core
> Affects Versions: 1.0.0
> Reporter: Sarath Subramanian
> Assignee: Sarath Subramanian
> Priority: Major
> Fix For: 1.0.0
>
> Attachments: TAG PROPAGATION IN ATLAS v.1.pdf,
> tag_propagation_rest_api
>
>
> {color:#172b4d}Scalable way to quickly and efficiently propagate tags for
> efficient searches and tag based security. Likewise tags for derivative
> dataset should be inherited from the parent. For example, if an entity is
> tagged "PII" then resulting entity created from a CTAS operation should also
> be tagged "secret" to maintain the classification of the parent. In the case
> where 2 or more datasets are aggregated the derivative dataset should be a
> union of all parent tags.{color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
