Project

General

Profile

Bug #22929

Workflow Support for jobs whose output is (great-)grandkids of input

Added by Marc Mengel 2 months ago. Updated 23 days ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
Start date:
08/01/2019
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
First Occurred:
Scope:
Internal
Experiment:
-
Stakeholders:
Duration:

Description

If a given stage of a workflow does multiple stages, such that the output of the job is the grandchild or more distant descendant) of the input, our dependency dataset generation doesn't work; and the current workaround of declaring the dependency dataset(s) in the job doesn't do recoveries right...


Subtasks

Task #23035: Add an integer output_ancestor_depth field to CampaignStage, defaulting to 1ClosedStephen White

Feature #23190: Actually support grankid, etc. output filesResolvedMarc Mengel


Related issues

Has duplicate Production Operations Management Service (POMS) - Feature #22885: Need kid/grandkid level on files for dependenciesResolved07/09/2019

History

#1 Updated by Marc Mengel about 2 months ago

  • Start date changed from 07/12/2019 to 08/01/2019
  • Due date set to 08/01/2019

due to changes in a related task: #23035

#2 Updated by Marc Mengel about 2 months ago

  • Has duplicate Feature #22885: Need kid/grandkid level on files for dependencies added

#3 Updated by Marc Mengel 23 days ago

  • Due date set to 08/29/2019

due to changes in a related task: #23190



Also available in: Atom PDF