Versions Compared

Old Version 3

changes.mady.by.user Deepak Wadhwani

Saved on

compared with

New Version 4

changes.mady.by.user Deepak Wadhwani

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Today, Tracker pipelines are shown on Program level. If programs are part of workflows, the user could choose to look at the Lineage at Workflow level. This would mean that the programs that are associated with the same workflows, can be "collapsed" together and shown as one workflow instead of multiple programs. 

This also includes removing the temporary datasets that could be created as a part of workflows.

 

API Changes: 

The two choices for APIs: 

  1. Collapse on Program: The API will request collapse=workflow for this view. If collapse=workflow is not provided then, the workflow fields are filled (if applicable) but relations are not collapsed. This approach is an extension of the collapse approach used today. But since workflows are also programs, it has the ambiguity when collapsing on "programs" because it still shows workflows. 
  2. Group-by on Workflow: In addition to the collapse, if a group-by is provided, it can be used as group-by=workflow and the programs that dont have workflows associated are left as it is. This approach also has some level of ambiguity listed above but is extensible if in future there is a requirement for group-by on application. [Because collapse workflow is confusing if there are no workflows present]  

Implementation Changes: 

  1. In the "programs" section: the ProgramId of the Program will be replaced by ProgramId of the workflow if the program is associated with a workflow. If not the Programs show as it is. 
  2. In the "relations" section: a new field called "workflow" will be added for all the relations that could be collapsed based on workflows. The programs field will be a collection of all the programs that were collapsed to form this workflow.  The API will request collapse=workflow for this view. If collapse= workflow is not provided then, the workflow fields are filled (if applicable) but relations are not collapsed. 

curl "http://127.0.0.1:10000/v3/namespaces/default/datasets/EmpAgg/lineage?collapse=access&collapse=run&collapse=component&collapse=program&end=now&levels=1&start=now-7d" | python -m json.tool

...