dsdt lineage

A history of a bundle came to be

Description

Every time you run a Disdat pipeline, Disdat tracks the code used to produce the data, the task's parameters, and the input bundles. This command gives you access to that information.

Usage

usage: dsdt lineage [-h] [-f] [-d DEPTH] uuid

Options

positional arguments:
  uuid                  Find lineage by bundle UUID

optional arguments:
  -h, --help            show this help message and exit
  -f, --follow          Follow lineage back through D levels.
  -d DEPTH, --depth DEPTH
                        Number of levels to follow (default is 3).

Examples

First, let's say we've run the following pipeline from our disdat-examples repo. 

$dsdt apply pipelines.dependent_tasks.B
...
===== Luigi Execution Summary =====

Scheduled 3 tasks of which:
* 3 ran successfully:
    - 1 A(...)
    - 1 B(...)
    - 1 DriverTask(...)

This progress looks :) because there were no failed tasks or missing dependencies

===== Luigi Execution Summary =====

We can then look at the lineage of bundle B

Previousdsdt initNextdsdt ls

Last updated

Was this helpful?