[ 
https://issues.apache.org/jira/browse/ATLAS-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pratik pandey updated ATLAS-2469:
---------------------------------
    Priority: Blocker  (was: Major)

> Tag propagation from object to child object or derivative asset
> ---------------------------------------------------------------
>
>                 Key: ATLAS-2469
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2469
>             Project: Atlas
>          Issue Type: New Feature
>            Reporter: pratik pandey
>            Assignee: pratik pandey
>            Priority: Blocker
>
> User Story:
> As a data steward i need a 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 "Secret" 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.
> Terms:
> * Child business terms should inherit the tags associated with the parent 
> term.
> * the option to propagate tags to child business terms in a hierarchy should 
> be provided
> * Ability to update the propagated tags manually via UI or through the API
> * Tagging a term should propagate to data assets that are already attached to 
> that business term as well
> Data assets
> * For supported components in HDP 2.6,if a derivative asset is created it 
> should inherit the tags and attributes from the original asset.
> * the option to propagate tags to child entities should be provided (e.g. if 
> you tag a hdfs folder optionally tag all the files within it)
> * Ability to update the propagated tags manually via UI or through the API
> * Tagging a parent object should be inherited even after child creation 
> dynamically (unless a flag is set not to do this)
> * Derived data assets should have the tags of the original data asset.
> conflict resolution - if the different values for attributes then a UX dialog 
> that prompts user for action needs to be provided. Once resolved, the 
> resolved value will be carry forth to derivative dataset.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to