Changelog#

1.4.13 / 0.20.13 (libraries)#

New#

• OpExecutionContext.add_output_metadata can now be called multiple times per output.

Bugfixes#

• The double evaluation of log messages in sensor logging has been fixed (thanks @janosroden !)
• Cron schedules targeting leap day (ending with 29 2 *) no longer cause exceptions in the UI or daemon.
• Previously, if multiple partitioned observable_source_assets with different partition definitions existed in the same code location, runs targeting those assets could fail to launch. This has been fixed.
• When using AutoMaterializePolicies with assets that depended on prior partitions of themselves, updating the start_date of their underlying PartitionsDefinition could result in runs being launched for partitions that no longer existed. This has been fixed.
• Fixed an issue where auto-materilization could sometimes produce duplicate runs if there was an error in the middle of an auto-materialization tick.
• [dagster-census] A recent change to the Census API broke compatibility with this integration. This has been fixed (thanks @ldnicolasmay!)
• [dagster-dbt] Fixed an issue where DagsterDbtTranslator did not properly invoke get_auto_materialize_policy and get_freshness_policy for load_assets_from_dbt_project.
• [ui] Fixed a number of interaction bugs with the Launchpad config editor, including issues with newlines and multiple cursors.
• [ui] Asset keys and partitions presented in the asset checks UI are sorted to avoid flickering.
• [ui] Backfill actions (terminate backfill runs, cancel backfill submission) are now available from an actions menu on the asset backfill details page.

Community Contributions#

• Typo fix in run monitoring docs (thanks c0dk)!
• Grammar fixes in testing docs (thanks sonnyarora)!
• Typo fix in contribution docs (thanks tab1tha)!

Experimental#

• [dagster-dbt][asset checks] Added support to model dbt tests as Dagster asset checks.
• [asset checks] Added @graph_asset support. This can be used to implement blocking checks, by raising an exception if the check fails.
• [asset checks] Fixed @multi_asset subsetting, so only checks which target assets in the subset will execute.
• [asset checks] AssetCheckSpecs will now cause an error at definition time if they target an asset other than the one they’re defined on.
• [asset checks] The status of asset checks now appears in the asset graph and asset graph sidebar.

Dagster Cloud#

• [Experimental] Added support for freeing global op concurrency slots after runs have finished, using the deployment setting: run_monitoring > free_slots_after_run_end_seconds

1.4.12 / 0.20.12 (libraries)#

New#

• The context object now has an asset_key property to get the AssetKey of the current asset.
• Performance improvements to the auto-materialize daemon when running on large asset graphs.
• The dagster dev and dagster-daemon run commands now include a --log-level argument that allows you to customize the logger level threshold.
• [dagster-airbyte] AirbyteResource now includes a poll_interval key that allows you to configure how often it checks an Airbyte sync’s status.

Bugfixes#

• Fixed an issue where the dagster scheduler would sometimes raise an error if a schedule set its cron_schedule to a list of strings and also had its default status set to AUTOMATICALLY_RUNNING.
• Fixed an issue where the auto-materialize daemon would sometimes raise a RecursionError when processing asset graphs with long upstream dependency chains.
• [ui] Fixed an issue where the Raw Compute Logs dropdown on the Run page sometimes didn’t show the current step name or properly account for retried steps.

Community Contributions#

• [dagster-databricks] Fixed a regression causing DatabricksStepLauncher to fail. Thanks @zyd14!
• Fixed an issue where Dagster raised an exception when combining observable source assets with multiple partitions definitions. Thanks @aroig!
• [dagster-databricks] Added support for client authentication with OAuth. Thanks @zyd14!
• [dagster-databricks] Added support for workspace and volumes init scripts in the databricks client. Thanks @zyd14!
• Fixed a missing import in our docs. Thanks @C0DK!

Experimental#

• Asset checks are now displayed in the asset graph and sidebar.

• [Breaking] Asset check severity is now set at runtime on AssetCheckResult instead of in the @asset_check definition. Now you can define one check that either errors or warns depending on your check logic. ERROR severity no longer causes the run to fail. We plan to reintroduce this functionality with a different API.

• [Breaking] @asset_check now requires the asset= argument, even if the asset is passed as an input to the decorated function. Example:

  @asset_check(asset=my_asset)
  def my_check(my_asset) -> AssetCheckResult:
      ...
  

• [Breaking] AssetCheckSpec now takes asset= instead of asset_key=, and can accept either a key or an asset definition.

• [Bugfix] Asset checks now work on assets with key_prefix set.

• [Bugfix] Execution failure asset checks are now displayed correctly on the checks tab.

Documentation#

• [dagster-dbt] Added example of invoking DbtCliResource in custom asset/op to API docs.
• [dagster-dbt] Added reference to explain how a dbt manifest can be created at run time or build time.
• [dagster-dbt] Added reference to outline the steps required to deploy a Dagster and dbt project in CI/CD.
• Miscellaneous fixes to broken links and typos.

1.4.11 / 0.20.11 (libraries)#

New#

• Dagster code servers now wait to shut down until any calls that they are running have finished, preventing them from stopping while in the middle of executing sensor ticks or other long-running operations.
• The dagster execute job cli now accepts —-op-selection (thanks @silent-lad!)
• [ui] Option (Alt) + R now reloads all code locations (OSS only)

Bugfixes#

• Adds a check to validate partition mappings when directly constructing AssetsDefinition instances.
• Assets invoked in composition functions like @graph and @job now work again, fixing a regression introduced in 1.4.5.
• Fixed an issue where a race condition with parallel runs materializing the same asset could cause a run to raise a RecursionError during execution.
• Fixed an issue where including a resource in both a schedule and a job raised a “Cannot specify resource requirements” exception when the definitions were loaded.
• The ins argument to graph_asset is now respected correctly.
• Fixed an issue where the daemon process could sometimes stop with a heartbeat failure when the first sensor it ran took a long time to execute.
• Fixed an issue where dagster dev failed on startup when the DAGSTER_GRPC_PORT `environment variable was set in the environment.
• deps arguments for an asset can now be specified as an iterable instead of a sequence, allowing for sets to be passed.
• [dagster-aws] Fixed a bug where the S3PickleIOManager didn’t correctly handle missing partitions when allow_missing_partitions was set. Thanks @o-sirawat!
• [dagster-k8s] in the helm chart, the daemon securityContext setting now applies correctly to all init containers (thanks @maowerner!)

Community Contributions#

• [dagster-databricks] Migrated to use new official databricks Python SDK. Thanks @judahrand!

Experimental#

• New APIs for defining and executing checks on software-defined assets. These APIs are very early and subject to change. The corresponding UI has limited functionality. Docs
• Adds a new auto-materialize skip rule AutoMaterializeRule.skip_on_not_all_parents_updated that enforces that an asset can only be materialized if all parents have been materialized since the asset's last materialization.
• Exposed an auto-materialize skip rule – AutoMaterializeRule.skip_on_parent_missing –which is already part of the behavior of the default auto-materialize policy.
• Auto-materialize evaluation history will now be stored for 1 month, instead of 1 week.
• The auto-materialize asset daemon now includes more logs about what it’s doing for each asset in each tick in the Dagster Daemon process output.

Documentation#

• [dagster-dbt] Added reference docs for dagster-dbt project scaffold.

Dagster Cloud#

• Fixed an issue where the Docker agent would sometimes fail to load code locations with long names with a hostname connection error.

1.4.10 / 0.20.10 (libraries)#

Bugfixes#

• [dagster-webserver] Fixed an issue that broke loading static files on Windows.

1.4.9 / 0.20.9 (libraries)#

Bugfixes#

• [dagster-webserver] Fixed an issue that caused some missing icons in the UI.