Rebuild behavior

Normal Explicit Only rebuild an existing partition when it's explicitly asked Only rebuild the dataset when it's explicitly asked Write-protected Never rebuild an existing partition, even when explicitly asked Never rebuild the dataset, even when explicitly asked

Cross-project build behavior

Inherit global setting Stop at this dataset Continue recursion

Virtualizable in build

When building a merged pipeline, may the data of this dataset not be materialized? Strongly increases merged pipeline performance.

Missing partitions as empty

WARNING: This option is experimental and unsupported. It will only work for some kinds of recipes and datasets. When a missing partition is requested as source of a build, consider as empty instead of failing. Useful if you have "holes" in a time partitioning.

Empty as not ready

If the dataset or partition is empty, consider it as not ready, so that the downstream recipes will not run.

Flow epoch

Advanced partitioning use cases.

Change tracking

The dataset is considered modified whenever the marker file changes, independently of modifications on the actual dataset files

Type system version

If enabled, auto-run Data Quality rules in error will NOT fail the parent recipe run, hence allowing the downstream recipes run in the context of a recursive build. Read the documentation to learn more.

Flow

Custom properties