-
Type: Sub-task
-
Resolution: Fixed
-
Priority: Major
-
Affects Version/s: master
-
Component/s: CLI: pegasus-exitcode, Integrity Checking, Pegasus Planner
-
None
In hierarchal workflows, we can have data dependencies between sub workflows i.e a file maybe created by a DAX job A that might be needed when the sub workflow corresponding to child DAX job B executes.
Usually, we have handled this using cache files that the planner writes out in the submit directory, when a workflow is planned. However, this cache file does not contain any checksums of files that maybe created as the workflow is run.
These checksums should also be propagated across workflows similar to cache files.