Closed ghukill closed 5 years ago
Methods are in place, add_input_job
and remove_input_job
, but holding off on anything further at this point.
By including as input, a Job that was run after -- specifically, with a higher Job id
-- it throws off the simplistic lineage re-run order that was id
based. This relates to issue https://github.com/WSULib/combine/issues/322. Keeping open for now, until this is resolved.
Methods in place, more nuanced downstream lineage through topographic sorting. Closing.
Everything is in place for the ability to drop / add Input Jobs for a Job. For example, assume:
If we wanted to include
C
as an input job forB
, we would have to either removeB
and recreate with same settings, but includingC
, or merge to a new JobD
. But even then, we might want the actions performed withB
on records fromC
, which would not be the case withD
.Best case, we can add
C
as an input Job forB
: