Closed tangobravo62 closed 3 years ago
This is implemented. Example of output:
"id": 1667,
"jobState": "STARTED",
"jobSteps": [
{
"id": 1681,
"jobStepState": "WAITING_INPUT",
"outputProductClass": "PTM_L2B",
"predecessors": []
},
{
"id": 1668,
"jobStepState": "WAITING_INPUT",
"outputProductClass": "PTM_L3",
"predecessors": [
{
"id": 1672
},
{
"id": 1681
}
]
},
{
"id": 1672,
"jobStepState": "WAITING_INPUT",
"outputProductClass": "PTM_L2A",
"predecessors": [
{
"id": 1675
}
]
},
{
"id": 1675,
"jobStepState": "COMPLETED",
"outputProductClass": "L1B_______",
"predecessors": []
}
]
}
While it is possible to deduce the dependencies between the job steps of a job from the database, it would be desirable to have a convenience method, which returns the immediate predecessors for each job step of a job, e. g.
GET jobs/graph/{id}
returns something like: