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

Sarath Subramanian commented on ATLAS-2456:
-------------------------------------------

[~davidrad],

1) Yes, the entity will have both assigned classification and propagated 
classifications each having different attributes. In the code this is handled 
by creating an edge (propagated) for propagated classifications. So an entity 
can be associated with only one classification type but can have any number of 
propagated classification types (from upstream entities).
4) Entity will provide both - associated and propagated classification 
information. The client will need to decide on which classification value to 
work on. 
5) Yes, only one classification of a type is allowed for an entity, exception 
will be thrown if same classification is added again.
6) Yes, propagated classifications will also follow the 
classification-entitytype restriction rules.
7) Both 'confidentiality' and its subclass will share the same confidentiality 
'level' attribute, hence will only have a single value for 'level' attribute. 
There won't be a conflict for the shared attribute value.

 

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

Reply via email to