1.4.17 / 0.20.17 (libraries)

New

• [dagster-dbt] DbtCliResource now enforces that the current installed version of dbt-core is at least version 1.4.0.
• [dagster-dbt] DbtCliResource now properly respects DBT_TARGET_PATH if it is set by the user. Artifacts from dbt invocations using DbtCliResource will now be placed in unique subdirectories of DBT_TARGET_PATH.

Bugfixes

• When executing a backfill that targets a range of time partitions in a single run, the partition_time_window attribute on OpExecutionContext and AssetExecutionContext now returns the time range, instead of raising an error.
• Fixed an issue where the asset backfill page raised a GraphQL error for backfills that targeted different partitions per-asset.
• Fixed job_name property on the result object of build_hook_context.

Experimental

• AssetSpec has been added as a new way to declare the assets produced by @multi_asset.
• AssetDep type allows you to specify upstream dependencies with partition mappings when using the deps parameter of @asset and AssetSpec.
• [dagster-ext] report_asset_check method added to ExtContext.
• [dagster-ext] ext clients now must use yield from to forward reported materializations and asset check results to Dagster. Results reported from ext that are not yielded will raise an error.

Documentation

• The Dagster UI documentation got an overhaul! We’ve updated all our screenshots and added a number of previously undocumented pages/features, including:
  • The Overview page, aka the Factory Floor
  • Job run compute logs
  • Global asset lineage
  • Overview > Resources
• The Resources documentation has been updated to include additional context about using resources, as well as when to use os.getenv() versus Dagster’s EnvVar.
• Information about custom loggers has been moved from the Loggers documentation to its own page, Custom loggers.