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

Srikanth Venkat updated ATLAS-3133:
-----------------------------------
    Description: 
Background: The current process metadata model within Atlas does not track 
multiple instances of execution of the same process. For example if we run same 
DDL (e.g. insert into table A select * from table B, C) multiple times Atlas 
does not capture the multiple instances of execution of the same logical 
process. 

User story: As a compliance admin or data steward, I need to be able to track 
multiple executions of the same process or pipeline that were done at different 
times and relate them to the logical process so that I can understand 
traceability and how different instances of my data pipelining operations 
performed over time.

Acceptance Criteria:

1) Every new instance of process execution is captured with the appropriate 
metadata for the process along with context (who, what, when)

2) One can navigate between process and process execution in Atlas UI and 
explore relevant metadata of each entity

3) Process nodes in lineage view display high level information about number of 
process executions associated with a particular process node.

 

 

 

 

  was:
Background: The current Atlas process metadata model within Atlas does not 
track multiple instances of execution of the same process. For example if we 
run same DDL (e.g. insert into table A select * from table B, C) multiple times 
Atlas does not capture the multiple instances of execution of the same logical 
process. 

User story: As a compliance admin or data steward, I need to be able to track 
multiple executions of the same process or pipeline that were done at different 
times and relate them to the logical process so that I can provide traceability 
and understand how different instances of my data pipelining operations 
performed over time.

Acceptance Criteria:

1) Every new instance of process execution is captured with the appropriate 
metadata for the process along with context (who, what, when)

2) One can navigate between process and process execution in Atlas UI and 
explore relevant metadata

3) Process nodes in lineage display high level information about number of 
process executions associated with a particular process node.

 

 

 

 


> Capture metadata for different executions of the same process in Atlas
> ----------------------------------------------------------------------
>
>                 Key: ATLAS-3133
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3133
>             Project: Atlas
>          Issue Type: New Feature
>          Components:  atlas-core, atlas-webui
>            Reporter: Srikanth Venkat
>            Assignee: Aadarsh Jajodia
>            Priority: Critical
>         Attachments: 
> 0001-ATLAS-3133-Adding-support-for-Process-Executions-in-.patch, Adding 
> Process Executions In Atlas(Community).pdf
>
>
> Background: The current process metadata model within Atlas does not track 
> multiple instances of execution of the same process. For example if we run 
> same DDL (e.g. insert into table A select * from table B, C) multiple times 
> Atlas does not capture the multiple instances of execution of the same 
> logical process. 
> User story: As a compliance admin or data steward, I need to be able to track 
> multiple executions of the same process or pipeline that were done at 
> different times and relate them to the logical process so that I can 
> understand traceability and how different instances of my data pipelining 
> operations performed over time.
> Acceptance Criteria:
> 1) Every new instance of process execution is captured with the appropriate 
> metadata for the process along with context (who, what, when)
> 2) One can navigate between process and process execution in Atlas UI and 
> explore relevant metadata of each entity
> 3) Process nodes in lineage view display high level information about number 
> of process executions associated with a particular process node.
>  
>  
>  
>  



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

Reply via email to