dagster-io/dagster 1.3.11

1.3.11 (core) / 0.19.11 (libraries)

on GitHub

New

• Assets with lazy auto-materialize policies are no longer auto-materialized if they are missing but don’t need to be materialized in order to help downstream assets meet their freshness policies.
• [ui] The descriptions of auto-materialize policies in the UI now include their skip conditions along with their materialization conditions.
• [dagster-dbt] Customized asset keys can now be specified for nodes in the dbt project, using meta.dagster.asset_key. This field takes in a list of strings that are used as the components of the generated AssetKey.

version: 2

models:
  - name: users
    config:
      meta:
        dagster:
          asset_key: ["my", "custom", "asset_key"]

• [dagster-dbt] Customized groups can now be specified for models in the dbt project, using meta.dagster.group. This field takes in a string that is used as the Dagster group for the generated software-defined asset corresponding to the dbt model.

version: 2

models:
  - name: users
    config:
      meta:
        dagster:
          group: "my_group"

Bugfixes

• Fixed an issue where the dagster-msteams and dagster-mlflow packages could be installed with incompatible versions of the dagster package due to a missing pin.
• Fixed an issue where the dagster-daemon run command sometimes kept code server subprocesses open longer than it needed to, making the process use more memory.
• Previously, when using @observable_source_assets with AutoMaterializePolicies, it was possible for downstream assets to get “stuck”, not getting materialized when other upstream assets changed, or for multiple down materializations to be kicked off in response to the same version being observed multiple times. This has been fixed.
• Fixed a case where the materialization count for partitioned assets could be wrong.
• Fixed an error which arose when trying to request resources within run failure sensors.
• [dagster-wandb] Fixed handling for multi-dimensional partitions. Thanks @chrishiste

Experimental

• [dagster-dbt] improvements to @dbt_assets
  • project_dir and target_path in DbtCliTask are converted from type str to type pathlib.Path.
  • In the case that dbt logs are not emitted as json, the log will still be redirected to be printed in the Dagster compute logs, under stdout.

Documentation

• Fixed a typo in dagster_aws S3 resources. Thanks @akan72
• Fixed a typo in link on the Dagster Instance page. Thanks @PeterJCLaw