New

• Asset backfills launched from the asset graph now respect partition mappings. For example, if partition N of asset2 depends on partition N-1 of asset1, and both of those partitions are included in a backfill, asset2’s partition N won’t be backfilled until asset1’s partition N-1 has been materialized.
• Asset backfills launched from the asset graph will now only materialize each non-partitioned asset once - after all upstream partitions within the backfill have been materialized.
• Executors can now be configured with a tag_concurrency_limits key that allows you to specify limits on the number of ops with certain tags that can be executing at once within a single run. See the docs for more information.
• ExecuteInProcessResult, the type returned by materialize, materialize_to_memory, and execute_in_process, now has an asset_value method that allows you to fetch output values by asset key.
• AssetIns can now accept Nothing for their dagster_type, which allows omitting the input from the parameters of the @asset- or @multi_asset- decorated function. This is useful when you want to specify a partition mapping or metadata for a non-managed input.
• The start_offset and end_offset arguments of TimeWindowPartitionMapping now work across TimeWindowPartitionsDefinitions with different start dates and times.
• If add_output_metadata is called multiple times within an op, asset, or IO manager handle_output, the values will now be merged, instead of later dictionaries overwriting earlier ones.
• materialize and materialize_to_memory now both accept a tags argument.
• Added SingleDimensionDependencyMapping, a PartitionMapping object that defines a correspondence between an upstream single-dimensional partitions definition and a downstream MultiPartitionsDefinition.
• The RUN_DEQUEUED event has been removed from the event log, since it was duplicative with the RUN_STARTING event.
• When an Exception is raised during the execution of an op or asset, Dagit will now include the original Exception that was raised, even if it was caught and another Exception was raised instead. Previously, Dagit would only show exception chains if the Exception was included using the raise Exception() from e syntax.
• [dagit] The Asset Catalog table in Dagit is now a virtualized infinite-scroll table. It is searchable and filterable just as before, and you can now choose assets for bulk materialization without having to select across pages.
• [dagit] Restored some metadata to the Code Locations table, including image, python file, and module name.
• [dagit] Viewing a partition on the asset details page now shows both the latest materialization and also all observations about that materialization.
• [dagit] Improved performance of the loading time for the backfills page
• [dagit] Improved performance when materializing assets with very large partition sets
• [dagit] Moving around asset and op graphs while selecting nodes is easier - drag gestures no longer clear your selection.
• [dagster-k8s] The Dagster Helm chart now allows you to set an arbitrary kubernetes config dictionary to be included in the launched job and pod for each run, using the runK8sConfig key in the k8sRunLauncher section. See the docs for more information.
• [dagster-k8s] securityContext can now be set in the k8sRunLauncher section of the Dagster Helm chart.
• [dagster-aws] The EcsRunLauncher can now be configured with cpu and memory resources for each launched job. Previously, individual jobs needed to be tagged with CPU and memory resources. See the docs for more information.
• [dagster-aws] The S3ComputeLogManager now takes in an argument upload_extra_args which are passed through as the ExtraArgs parameter to the file upload call.
• [dagster-airflow] added make_dagster_definitions_from_airflow_dags_path and make_dagster_definitions_from_airflow_dag_bag which are passed through as the ExtraArgs parameter to the file upload call.

Bugfixes

• Fixed a bug where ad-hoc materializations of assets were not correctly retrieving metadata of upstream assets.
• Fixed a bug that caused ExperimentalWarnings related to LogicalVersions to appear even when version-based staleness was not in use.
• Fixed a bug in the asset reconciliation sensor that caused multi-assets to be reconciled when some, but not all, of the assets they depended on, were reconciled.
• Fixed a bug in the asset reconciliation sensor that caused it to only act on one materialization per asset per tick, even when multiple partitions of an asset were materialized.
• Fixed a bug in the asset reconciliation sensor that caused it to never attempt to rematerialize assets which failed in their last execution. Now, it will launch the next materialization for a given asset at the same time that it would have if the original run had completed successfully.
• The load_assets_from_modules and load_assets_from_package_module utilities now will also load cacheable assets from the specified modules.
• The dequeue_num_workers config setting on QueuedRunCoordinatoris now respected.
• [dagit] Fixed a bug that caused a “Maximum recursion depth exceeded” error when viewing partitioned assets with self-dependencies.
• [dagit] Fixed a bug where “Definitions loaded” notifications would constantly show up in cases where there were multiple dagit hosts running.
• [dagit] Assets that are partitioned no longer erroneously appear "Stale" in the asset graph.
• [dagit] Assets with a freshness policy no longer appear stale when they are still meeting their freshness policy.
• [dagit] Viewing Dagit in Firefox no longer results in erroneous truncation of labels in the left sidebar.
• [dagit] Timestamps on the asset graph are smaller and have an appropriate click target.
• [dagster-databricks] The databricks_pyspark_step_launcher will now cancel the relevant databricks job if the Dagster step execution is interrupted.
• [dagster-databricks] Previously, the databricks_pyspark_step_launcher could exit with an unhelpful error after receiving an HTTPError from databricks with an empty message. This has been fixed.
• [dagster-snowflake] Fixed a bug where calling execute_queries or execute_query on a snowflake_resource would raise an error unless the parameters argument was explicitly set.
• [dagster-aws] Fixed a bug in the EcsRunLauncher when launching many runs in parallel. Previously, each run risked hitting a ClientError in AWS for registering too many concurrent changes to the same task definition family. Now, the EcsRunLauncher recovers gracefully from this error by retrying it with backoff.
• [dagster-airflow] Added make_dagster_definitions_from_airflow_dags_path and make_dagster_definitions_from_airflow_dag_bag for creating Dagster definitions from a given airflow Dag file path or DagBag

Community Contributions

• Fixed a metadata loading error in UPathIOManager, thanks @danielgafni!
• [dagster-aws]FakeS3Session now includes additional functions and improvements to align with the boto3 S3 client API, thanks @asharov!
• Typo fix from @vpicavet, thank you!
• Repository license file year and company update, thanks @vwbusguy!

Experimental

• Added experimental BranchingIOManager to model use case where you wish to read upstream assets from production environments and write them into a development environment.
• Add create_repository_using_definitions_args to allow for the creation of named repositories.
• Added the ability to use Python 3 typing to define and access op and asset config.
• [dagster-dbt] Added DbtManifestAssetSelection, which allows you to define selections of assets loaded from a dbt manifest using dbt selection syntax (e.g. tag:foo,path:marts/finance).

Documentation

• There’s now only one Dagster Cloud Getting Started guide, which includes instructions for both Hybrid and Serverless deployment setups.
• Lots of updates throughout the docs to clean up remaining references to @repository, replacing them with Definitions.
• Lots of updates to the dagster-airflow documentation, a tutorial for getting started with Dagster from an airflow background, a migration guide for going to Dagster from Airflow and a terminology/concept map for Airflow onto Dagster.

All Changes

https://github.com/dagster-io/dagster/compare/1.1.7...1.1.8

New

• Definitions is no longer marked as experimental and is the preferred API over @repository for new users of Dagster. Examples, tutorials, and documentation have largely ported to this new API. No migration is needed. Please see GitHub discussion for more details.
• The “Workspace” section of Dagit has been removed. All definitions for your code locations can be accessed via the “Deployment” section of the app. Just as in the old Workspace summary page, each code location will show counts of its available jobs, assets, schedules, and sensors. Additionally, the code locations page is now available at /locations.
• Lagged / rolling window partition mappings: TimeWindowPartitionMapping now accepts start_offset and end_offset arguments that allow specifying that time partitions depend on earlier or later time partitions of upstream assets.
• Asset partitions can now depend on earlier time partitions of the same asset. The asset reconciliation sensor will respect these dependencies when requesting runs.
• dagit can now accept multiple arguments for the -m and -f flags. For each argument a new code location is loaded.
• Schedules created by build_schedule_from_partitioned_job now execute more performantly - in constant time, rather than linear in the number of partitions.
• The QueuedRunCoordinator now supports options dequeue_use_threads and dequeue_num_workers options to enable concurrent run dequeue operations for greater throughput.
• [dagster-dbt] load_assets_from_dbt_project, load_assets_from_dbt_manifest, and load_assets_from_dbt_cloud_job now support applying freshness policies to loaded nodes. To do so, you can apply dagster_freshness_policy config directly in your dbt project, i.e. config(dagster_freshness_policy={"maximum_lag_minutes": 60}) would result in the corresponding asset being assigned a FreshnessPolicy(maximum_lag_minutes=60).
• The DAGSTER_RUN_JOB_NAME environment variable is now set in containerized environments spun up by our run launchers and executor.
• [dagster-airflow] make_dagster_repo_from_airflow_dags_path ,make_dagster_job_from_airflow_dag and make_dagster_repo_from_airflow_dag_bag have a new connections parameter which allows for configuring the airflow connections used by migrated dags.

Bugfixes

• Fixed a bug where the log property was not available on the RunStatusSensorContext context object provided for run status sensors for sensor logging.

• Fixed a bug where the re-execute button on runs of asset jobs would incorrectly show warning icon, indicating that the pipeline code may have changed since you last ran it.

• Fixed an issue which would cause metadata supplied to graph-backed assets to not be viewable in the UI.

• Fixed an issue where schedules often took up to 5 seconds to start after their tick time.

• Fixed an issue where Dagster failed to load a dagster.yaml file that specified the folder to use for sqlite storage in the dagster.yaml file using an environment variable.

• Fixed an issue which would cause the k8s/docker executors to unnecessarily reload CacheableAssetsDefinitions (such as those created when using load_assets_from_dbt_cloud_job) on each step execution.

• [dagster-airbyte] Fixed an issue where Python-defined Airbyte sources and destinations were occasionally recreated unnecessarily.

• Fixed an issue with build_asset_reconciliation_sensor that would cause it to ignore in-progress runs in some cases.

• Fixed a bug where GQL errors would be thrown in the asset explorer when a previously materialized asset had its dependencies changed.

• [dagster-airbyte] Fixed an error when generating assets for normalization table for connections with non-object streams.

• [dagster-dbt] Fixed an error where dbt Cloud jobs with dbt run and dbt run-operation were incorrectly validated.

• [dagster-airflow] use_ephemeral_airflow_db now works when running within a PEX deployment artifact.

Documentation

• New documentation for Code locations and how to define one using Definitions
• Lots of updates throughout the docs to reflect the recommended usage of Definitions. Any content not ported to Definitions in this release is in the process of being updated.
• New documentation for dagster-airflow on how to start writing dagster code from an airflow background.

All Changes

https://github.com/dagster-io/dagster/compare/1.1.6...1.1.7

New

• [dagit] Throughout Dagit, when the default repository name __repository__ is used for a repo, only the code location name will be shown. This change also applies to URL paths.
• [dagster-dbt] When attempting to generate software-defined assets from a dbt Cloud job, an error is now raised if none are created.
• [dagster-dbt] Software-defined assets can now be generated for dbt Cloud jobs that execute multiple commands.

Bugfixes

• Fixed a bug that caused load_asset_value to error with the default IO manager when a partition_key argument was provided.
• Previously, trying to access context.partition_key or context.asset_partition_key_for_output when invoking an asset directly (e.g. in a unit test) would result in an error. This has been fixed.
• Failure hooks now receive the original exception instead of RetryRequested when using a retry policy.
• The LocationStateChange GraphQL subscription has been fixed (thanks @****roeij !)**
• Fixed a bug where a sqlite3.ProgrammingError error was raised when creating an ephemeral DagsterInstance, most commonly when build_resources was called without passing in an instance parameter.
• [dagstermill] Jupyter notebooks now correctly render in Dagit on Windows machines.
• [dagster-duckdb-pyspark] New duckdb_pyspark_io_manager helper to automatically create a DuckDB I/O manager that can store and load PySpark DataFrames.
• [dagster-mysql] Fixed a bug where versions of mysql < 8.0.31 would raise an error on some run queries.
• [dagster-postgres] connection url param “options“ are no longer overwritten in dagit.
• [dagit] Dagit now allows backfills to be launched for asset jobs that have partitions and required config.
• [dagit] Dagit no longer renders the "Job in [email protected]" label incorrectly in Chrome v109.
• [dagit] Dagit's run list now shows improved labels on asset group runs of more than three assets
• [dagit] Dagit's run gantt chart now renders per-step resource initialization markers correctly.
• [dagit] In op and asset descriptions in Dagit, rendered markdown no longer includes extraneous escape slashes.
• Assorted typos and omissions fixed in the docs — thanks @C0DK and @akan72!

Experimental

• As an optional replacement of the workspace/repository concepts, a new Definitions entrypoint for tools and the UI has been added. A single Definitions object per code location may be instantiated, and accepts typed, named arguments, rather than the heterogenous list of definitions returned from an @repository-decorated function. To learn more about this feature, and provide feedback, please refer to the Github Discussion.
• [dagster-slack] A new make_slack_on_freshness_policy_status_change_sensor allows you to create a sensor to alert you when an asset is out of date with respect to its freshness policy (and when it’s back on time!)

Documentation

• Refreshed dagstermill guide and reference page https://docs.dagster.io/integrations/dagstermill
• New declarative scheduling guide: https://docs.dagster.io/guides/dagster/scheduling-assets
• New dagster-snowflake guide: https://docs.dagster.io/integrations/snowflake
• Added docs for asset code versioning: https://docs.dagster.io/concepts/assets/software-defined-assets#asset-code-versions
• Added docs for observable source assets: https://docs.dagster.io/concepts/assets/asset-observations#observable-source-assets

Bugfixes

• [dagit] Fixed an issue where the Partitions tab sometimes failed to load for asset jobs.

Community Contributions

• Fixed a typo in GCSComputeLogManager docstring (thanks reidab)!
• [dagster-airbyte] job cancellation on run termination is now optional. (Thanks adam-bloom)!
• [dagster-snowflake] Can now specify snowflake role in config to snowflake io manager (Thanks binhnefits)!
• [dagster-aws] A new AWS systems manager resource (thanks zyd14)!
• [dagstermill] Retry policy can now be set on dagstermill assets (thanks nickvazz)!
• Corrected typo in docs on metadata (thanks C0DK)!

New

• Added a job_name parameter to InputContext.
• Fixed inconsistent io manager behavior when using execute_in_process on a GraphDefinition (it would use the fs_io_manager instead of the in-memory io manager).
• Compute logs will now load in Dagit even when websocket connections are not supported.
• [dagit] A handful of changes have been made to our URLs:
  • The /instance URL path prefix has been removed. E.g. /instance/runs can now be found at /runs.
  • The /workspace URL path prefix has been changed to /locations. E.g. the URL for job my_job in repository [email protected] can now be found at /locations/[email protected]/jobs/my_job.
• [dagit] The “Workspace” navigation item in the top nav has been moved to be a tab under the “Deployment” section of the app, and is renamed to “Definitions”.
• [dagstermill] Dagster events can now be yielded from asset notebooks using dagstermill.yield_event.
• [dagstermill] Failed notebooks can be saved for inspection and debugging using the new save_on_notebook_failure parameter.
• [dagster-airflow] Added a new option use_ephemeral_airflow_db which will create a job run scoped airflow db for airflow dags running in dagster
• [dagster-dbt] Materializing software-defined assets using dbt Cloud jobs now supports partitions.
• [dagster-dbt] Materializing software-defined assets using dbt Cloud jobs now supports subsetting. Individual dbt Cloud models can be materialized, and the proper filters will be passed down to the dbt Cloud job.
• [dagster-dbt] Software-defined assets from dbt Cloud jobs now support configurable group names.
• [dagster-dbt] Software-defined assets from dbt Cloud jobs now support configurable AssetKeys.

Bugfixes

• Fixed regression starting in 1.0.16 for some compute log managers where an exception in the compute log manager setup/teardown would cause runs to fail.
• The S3 / GCS / Azure compute log managers now sanitize the optional prefix argument to prevent badly constructed paths.
• [dagit] The run filter typeahead no longer surfaces key-value pairs when searching for tag:. This resolves an issue where retrieving the available tags could cause significant performance problems. Tags can still be searched with freeform text, and by adding them via click on individual run rows.
• [dagit] Fixed an issue in the Runs tab for job snapshots, where the query would fail and no runs were shown.
• [dagit] Schedules defined with cron unions displayed “Invalid cron string” in Dagit. This has been resolved, and human-readable versions of all members of the union will now be shown.

Breaking Changes

• You can no longer set an output’s asset key by overriding get_output_asset_key on the IOManager handling the output. Previously, this was experimental and undocumented.

Experimental

• Sensor and schedule evaluation contexts now have an experimental log property, which log events that can later be viewed in Dagit. To enable these log views in dagit, navigate to the user settings and enable the Experimental schedule/sensor logging view option. Log links will now be available for sensor/schedule ticks where logs were emitted. Note: this feature is not available for users using the NoOpComputeLogManager.

Bugfixes

• Fixed a bug with the asset reconciliation sensor that caused duplicate runs to be submitted in situations where an asset has a different partitioning than its parents.
• Fixed a bug with the asset reconciliation sensor that caused it to error on time-partitioned assets.
• [dagster-snowflake] Fixed a bug when materializing partitions with the Snowflake I/O manager where sql BETWEEN was used to determine the section of the table to replace. BETWEEN included values from the next partition causing the I/O manager to erroneously delete those entries.
• [dagster-duckdb] Fixed a bug when materializing partitions with the DuckDB I/O manager where sql BETWEEN was used to determine the section of the table to replace. BETWEEN included values from the next partition causing the I/O manager to erroneously delete those entries.

Bugfixes

• In Dagit, assets that had been materialized prior to upgrading to 1.1.1 were showing as "Stale". This is now fixed.
• Schedules that were constructed with a list of cron strings previously rendered with an error in Dagit. This is now fixed.
• For users running dagit version >= 1.0.17 (or dagster-cloud) with dagster version < 1.0.17, errors could occur when hitting "Materialize All" and some other asset-related interactions. This has been fixed.

Major Changes since 1.0.0 (core) / 0.16.0 (libraries)

Core

• You can now create multi-dimensional partitions definitions for software-defined assets, through the MultiPartitionsDefinition API. In Dagit, you can filter and materialize certain partitions by providing ranges per-dimension, and view your materializations by dimension.
• The new asset reconciliation sensor automatically materializes assets that have never been materialized or whose upstream assets have changed since the last time they were materialized. It works with partitioned assets too. You can construct it using build_asset_reconciliation_sensor.
• You can now add a FreshnessPolicy to any of your software-defined assets, to specify how up-to-date you expect that asset to be. You can view the freshness status of each asset in Dagit, alert when assets are missing their targets using the @freshness_policy_sensor, and use the build_asset_reconciliation_sensor to make a sensor that automatically kick off runs to materialize assets based on their freshness policies.
• You can now version your asset ops and source assets to help you track which of your assets are stale. You can do this by assigning op_version s to software-defined assets or observation_fn s to SourceAssets. When a set of assets is versioned in this way, their “Upstream Changed” status will be based on whether upstream versions have changed, rather than on whether upstream assets have been re-materialized. You can launch runs that materialize only stale assets.
• The new @multi_asset_sensor decorator enables defining custom sensors that trigger based on the materializations of multiple assets. The context object supplied to the decorated function has methods to fetch latest materializations by asset key, as well as built-in cursor management to mark specific materializations as “consumed”, so that they won’t be returned in future ticks. It can also fetch materializations by partition and mark individual partitions as consumed.
• RepositoryDefinition now exposes a load_asset_value method, which accepts an asset key and invokes the asset’s I/O manager’s load_input function to load the asset as a Python object. This can be used in notebooks to do exploratory data analysis on assets.
• With the new asset_selection parameter on @sensor and SensorDefinition, you can now define a sensor that directly targets a selection of assets, instead of targeting a job.
• When running dagit or dagster-daemon locally, environment variables included in a .env file in the form KEY=value in the same folder as the command will be automatically included in the environment of any Dagster code that runs, allowing you to easily use environment variables during local development.

Dagit

• The Asset Graph has been redesigned to make better use of color to communicate asset health. New status indicators make it easy to spot missing and stale assets (even on large graphs!) and the UI updates in real-time as displayed assets are materialized.
• The Asset Details page has been redesigned and features a new side-by-side UI that makes it easier to inspect event metadata. A color-coded timeline on the partitions view allows you to drag-select a time range and inspect the metadata and status quickly. The new view also supports assets that have been partitioned across multiple dimensions.
• The new Workspace page helps you quickly find and navigate between all your Dagster definitions. It’s also been re-architected to load significantly faster when you have thousands of definitions.
• The Overview page is the new home for the live run timeline and helps you understand the status of all the jobs, schedules, sensors, and backfills across your entire deployment. The timeline is now grouped by repository and shows a run status rollup for each group.

Integrations

• dagster-dbt now supports generating software-defined assets from your dbt Cloud jobs.
• dagster-airbyte and dagster-fivetran now support automatically generating assets from your ETL connections using load_assets_from_airbyte_instance and load_assets_from_fivetran_instance.
• New dagster-duckdb integration: build_duckdb_io_manager allows you to build an I/O manager that stores and loads Pandas and PySpark DataFrames in DuckDB.

Database migration

• Optional database schema migration, which can be run via dagster instance migrate:
  • Improves Dagit performance by adding database indexes which should speed up the run view as well as a range of asset-based queries.
  • Enables multi-dimensional asset partitions and asset versioning.

Breaking Changes and Deprecations

• define_dagstermill_solid, a legacy API, has been removed from dagstermill. Use define_dagstermill_op or define_dagstermill_asset instead to create an op or asset from a Jupyter notebook, respectively.
• The internal ComputeLogManager API is marked as deprecated in favor of an updated interface: CapturedLogManager. It will be removed in 1.2.0. This should only affect dagster instances that have implemented a custom compute log manager.

Dependency Changes

• dagster-graphql and dagit now use version 3 of graphene

Since 1.0.17

New

• The new UPathIOManager base class is now a top-level Dagster export. This enables you to write a custom I/O manager that plugs stores data in any filesystem supported by universal-pathlib and uses different serialization format than pickle (Thanks Daniel Gafni!).
• The default fs_io_manager now inherits from the UPathIOManager, which means that its base_dir can be a path on any filesystem supported by universal-pathlib (Thanks Daniel Gafni!).
• build_asset_reconciliation_sensor now works with support partitioned assets.
• build_asset_reconciliation_sensor now launches runs to keep assets in line with their defined FreshnessPolicies.
• The FreshnessPolicy object is now exported from the top level dagster package.
• For assets with a FreshnessPolicy defined, their current freshness status will be rendered in the asset graph and asset details pages.
• The AWS, GCS, and Azure compute log managers now take an additional config argument upload_interval which specifies in seconds, the interval in which partial logs will be uploaded to the respective cloud storage. This can be used to display compute logs for long-running compute steps.
• When running dagit or dagster-daemon locally, environment variables included in a .env file in the form KEY=value in the same folder as the command will be automatically included in the environment of any Dagster code that runs, allowing you to easily test environment variables during local development.
• observable_source_asset decorator creates a SourceAsset with an associated observation_fn that should return a LogicalVersion, a new class that wraps a string expressing a version of an asset’s data value.
• [dagit] The asset graph now shows branded compute_kind tags for dbt, Airbyte, Fivetran, Python and more.
• [dagit] The asset details page now features a redesigned event viewer, and separate tabs for Partitions, Events, and Plots. This UI was previously behind a feature flag and is now generally available.
• [dagit] The asset graph UI has been revamped and makes better use of color to communicate asset status, especially in the zoomed-out view.
• [dagit] The asset catalog now shows freshness policies in the “Latest Run” column when they are defined on your assets.
• [dagit] The UI for launching backfills in Dagit has been simplified. Rather than selecting detailed ranges, the new UI allows you to select a large “range of interest” and materialize only the partitions of certain statuses within that range.
• [dagit] The partitions page of asset jobs has been updated to show per-asset status rather than per-op status, so that it shares the same terminology and color coding as other asset health views.
• [dagster-k8s] Added an execute_k8s_job function that can be called within any op to run an image within a Kubernetes job. The implementation is similar to the build-in k8s_job_op , but allows additional customization - for example, you can incorporate the output of a previous op into the launched Kubernetes job by passing it into execute_k8s_job. See the dagster-k8s API docs for more information.
• [dagster-databricks] Environment variables used by dagster cloud are now automatically set when submitting databricks jobs if they exist, thank you @zyd14!
• [dagstermill] define_dagstermill_asset now supports RetryPolicy . Thanks @nickvazz!
• [dagster-airbyte] When loading assets from an Airbyte instance using load_assets_from_airbyte_instance, users can now optionally customize asset names using connector_to_asset_key_fn.
• [dagster-fivetran] When loading assets from a Fivetran instance using load_assets_from_fivetran_instance, users can now alter the IO manager using io_manager_key or connector_to_io_manager_key_fn, and customize asset names using connector_to_asset_key_fn.

Bugfixes

• Fixed a bug where terminating runs from a backfill would fail without notice.
• Executing a subset of ops within a job that specifies its config value directly on the job, it no longer attempts to use that config value as the default. The default is still presented in the editable interface in dagit.
• [dagit] The partition step run matrix now reflects historical step status instead of just the last run’s step status for a particular partition.

Documentation

• Updated Environment variables and secrets docs with info/instructions for using local .env files
• Added a new example test to the Testing docs. This test verifies if Dagster code loads correctly by loading a Dagster repository and its definitions.

New

• With the new asset_selection parameter on @sensor and SensorDefinition, you can now define a sensor that directly targets a selection of assets, instead of targeting a job.
• materialize and materialize_to_memory now accept a raise_on_error argument, which allows you to determine whether to raise an Error if the run hits an error or just return as failed.
• (experimental) Dagster now supports multi-dimensional asset partitions, through a new MultiPartitionsDefinition object. An optional schema migration enables support for this feature (run via dagster instance migrate). Users who are not using this feature do not need to run the migration.
• You can now launch a run that targets a range of asset partitions, by supplying the "dagster/asset_partition_range_start" and "dagster/asset_partition_range_end" tags.
• [dagit] Asset and op graphs in Dagit now show integration logos, making it easier to identify assets backed by notebooks, DBT, Airbyte, and more.
• [dagit] a -db-pool-recycle cli flag (and dbPoolRecycle helm option) have been added to control how long the pooled connection dagit uses persists before recycle. The default of 1 hour is now respected by postgres (mysql previously already had a hard coded 1hr setting). Thanks @adam-bloom!
• [dagster-airbyte] Introduced the ability to specify output IO managers when using load_assets_from_airbyte_instance and load_assets_from_airbyte_project.
• [dagster-dbt] the dbt_cloud_resource resource configuration account_id can now be sourced from the environment. Thanks @sowusu-ba!
• [dagster-duckdb] The DuckDB integration improvements: PySpark DataFrames are now fully supported, “schema” can be specified via IO Manager config, and API documentation has been improved to include more examples
• [dagster-fivetran] Introduced experimental load_assets_from_fivetran_instance helper which automatically pulls assets from a Fivetran instance.
• [dagster-k8s] Fixed an issue where setting the securityContext configuration of the Dagit pod in the Helm chart didn’t apply to one of its containers. Thanks @jblawatt!

Bugfixes

• Fixed a bug that caused the asset_selection parameter of RunRequest to not be respected when used inside a schedule.
• Fixed a bug with health checks during delayed Op retries with the k8s_executor and docker_executor.
• [dagit] The asset graph now live-updates when assets fail to materialize due to op failures.
• [dagit] The "Materialize" button now respects the backfill permission for multi-run materializations.
• [dagit] Materializations without metadata are padded correctly in the run logs.
• [dagster-aws] Fixed an issue where setting the value of task_definition field in the EcsRunLauncher to an environment variable stopped working.
• [dagster-dbt] Add exposures in load_assets_from_dbt_manifest. This fixed then error when load_assets_from_dbt_manifest failed to load from dbt manifest with exposures. Thanks @sowusu-ba!
• [dagster-duckdb] In some examples, the duckdb config was incorrectly specified. This has been fixed.

Breaking Changes

• The behavior of the experimental asset reconciliation sensor, which is accessible via build_asset_reconciliation_sensor has changed to be more focused on reconciliation. It now materializes assets that have never been materialized before and avoids materializing assets that are “Upstream changed”. The build_asset_reconciliation_sensor API no longer accepts wait_for_in_progress_runs and wait_for_all_upstream arguments.

Documentation

• Added documentation outlining environment variable declaration and usage in Dagster code, including how to pass secrets.
• Fixed a typo on Dagster Instance page. Thanks @domsj!

All Changes

https://github.com/dagster-io/dagster/compare/1.0.16...1.0.17

New

• [dagit] The new Overview and Workspace pages have been enabled for all users, after being gated with a feature flag for the last several releases. These changes include design updates, virtualized tables, and more performant querying.
  • The top navigation has been updated to improve space allocation, with main nav links moved to the left.
  • “Overview” is the new Dagit home page and “factory floor” view, were you can find the run timeline, which now offers time-based pagination. The Overview section also contains pages with all of your jobs, schedules, sensors, and backfills. You can filter objects by name, and collapse or expand repository sections.
  • “Workspace” has been redesigned to offer a better summary of your repositories, and to use the same performant table views, querying, and filtering as in the Overview pages.
• @asset and @multi_asset now accept a retry_policy argument. (Thanks Adam Bloom!)
• When loading an input that depends on multiple partitions of an upstream asset, the fs_io_manager will now return a dictionary that maps partition keys to the stored values for those partitions. (Thanks andrewgryan!).
• JobDefinition.execute_in_process now accepts a run_config argument even when the job is partitioned. If supplied, the run config will be used instead of any config provided by the job’s PartitionedConfig.
• The run_request_for_partition method on jobs now accepts a run_config argument. If supplied, the run config will be used instead of any config provided by the job’s PartitionedConfig.
• The new NotebookMetadataValue can be used to report the location of executed jupyter notebooks, and Dagit will be able to render the notebook.
• Resolving asset dependencies within a group now works with multi-assets, as long as all the assets within the multi-asset are in the same group. (Thanks @peay!)
• UPathIOManager, a filesystem-agnostic IOManager base class has been added - (Thanks @danielgafni!)
• A threadpool option has been added for the scheduler daemon. This can be enabled via your dagster.yaml file; check out the docs.
• The default LocalComputeLogManager will capture compute logs by process instead of by step. This means that for the in_process executor, where all steps are executed in the same process, the captured compute logs for all steps in a run will be captured in the same file.
• [dagster-airflow] make_dagster_job_from_airflow_dag now supports airflow 2, there is also a new mock_xcom parameter that will mock all calls to made by operators to xcom.
• [helm] volume and volumeMount sections have been added for the dagit and daemon sections of the helm chart.

Bugfixes

• For partitioned asset jobs whose config is a hardcoded dictionary (rather than a PartitionedConfig), previously run_request_for_partition would produce a run with no config. Now, the run has the hardcoded dictionary as its config.
• Previously, asset inputs would be resolved to upstream assets in the same group that had the same name, even if the asset input already had a key prefix. Now, asset inputs are only resolved to upstream assets in the same group if the input path only has a single component.
• Previously, asset inputs could get resolved to outputs of the same AssetsDefinition, through group-based asset dependency resolution, which would later error because of a circular dependency. This has been fixed.
• Previously, the “Partition Status” and “Backfill Status” fields on the Backfill page in dagit were always incomplete and showed missing partitions. This has been fixed to accurately show the status of the backfill runs.
• [dagit] When viewing the config dialog for a run with a very long config, scrolling was broken and the “copy” button was not visible. This has been fixed.
• Executors now compress step worker arguments to avoid CLI length limits with large DAGs.
• [dagster-msteams] Longer messages can now be used in Teams HeroCard - (Thanks @jayhale!)

Documentation

• API docs for InputContext have been improved - (Thanks @peay!)
• [dagster-snowflake] Improved documentation for the Snowflake IO manager

All Changes

https://github.com/dagster-io/dagster/compare/1.0.15...1.0.16

New

• [dagit] The run timeline now shows all future schedule ticks for the visible time window, not just the next ten ticks.
• [dagit] Asset graph views in Dagit refresh as materialization events arrive, making it easier to watch your assets update in real-time.
• [dagster-airbyte] Added support for basic auth login to the Airbyte resource.
• Configuring a Python Log Level will now also apply to system logs created by Dagster during a run.

Bugfixes

• Fixed a bug that broke asset partition mappings when using the key_prefix with methods like load_assets_from_modules.
• [dagster-dbt] When running dbt Cloud jobs with the dbt_cloud_run_op, the op would emit a failure if the targeted job did not create a run_results.json artifact, even if this was the expected behavior. This has been fixed.
• Improved performance by adding database indexes which should speed up the run view as well as a range of asset-based queries. These migrations can be applied by running dagster instance migrate.
• An issue that would cause schedule/sensor latency in the daemon during workspace refreshes has been resolved.
• [dagit] Shift-clicking Materialize for partitioned assets now shows the asset launchpad, allowing you to launch execution of a partition with config.

Community Contributions

• Fixed a bug where asset keys with - were not being properly sanitized in some situations. Thanks @peay!
• [dagster-airbyte] A list of connection directories can now be specified in load_assets_from_airbyte_project. Thanks @adam-bloom!
• [dagster-gcp] Dagster will now retry connecting to GCS if it gets a ServiceUnavailable error. Thanks @cavila-evoliq!
• [dagster-postgres] Use of SQLAlchemy engine instead of psycopg2 when subscribing to PostgreSQL events. Thanks @peay!

Experimental

• [dagster-dbt] Added a display_raw_sql flag to the dbt asset loading functions. If set to False, this will remove the raw sql blobs from the asset descriptions. For large dbt projects, this can significantly reduce the size of the generated workspace snapshots.
• [dagit] A “New asset detail pages” feature flag available in Dagit’s settings allows you to preview some upcoming changes to the way historical materializations and partitions are viewed.

All Changes

https://github.com/dagster-io/dagster/compare/1.0.14...1.0.15

New

• Tags can now be provided to an asset reconciliation sensor and will be applied to all RunRequests returned by the sensor.
• If you don’t explicitly specify a DagsterType on a graph input, but all the inner inputs that the graph input maps to have the same DagsterType, the graph input’s DagsterType will be set to the the DagsterType of the inner inputs.
• [dagster-airbyte] load_assets_from_airbyte_project now caches the project data generated at repo load time so it does not have to be regenerated in subprocesses.
• [dagster-airbyte] Output table schema metadata is now generated at asset definition time when using load_assets_from_airbyte_instance or load_assets_from_airbyte_project.
• [dagit] The run timeline now groups all jobs by repository. You can collapse or expand each repository in this view by clicking the repository name. This state will be preserved locally. You can also hold Shift while clicking the repository name, and all repository groups will be collapsed or expanded accordingly.
• [dagit] In the launchpad view, a “Remove all” button is now available once you have accrued three or more tabs for that job, to make it easier to clear stale configuration tabs from view.
• [dagit] When scrolling through the asset catalog, the toolbar is now sticky. This makes it simpler to select multiple assets and materialize them without requiring you to scroll back to the top of the page.
• [dagit] A “Materialize” option has been added to the action menu on individual rows in the asset catalog view.
• [dagster-aws] The EcsRunLauncher now allows you to pass in a dictionary in the task_definition config field that specifies configuration for the task definition of the launched run, including role ARNs and a list of sidecar containers to include. Previously, the task definition could only be configured by passing in a task definition ARN or by basing the the task definition off of the task definition of the ECS task launching the run. See the docs for the full set of available config.

Bugfixes

• Previously, yielding a SkipReason within a multi-asset sensor (experimental) would raise an error. This has been fixed.
• [dagit] Previously, if you had a partitioned asset job and supplied a hardcoded dictionary of config to define_asset_job, you would run into a CheckError when launching the job from Dagit. This has been fixed.
• [dagit] When viewing the Runs section of Dagit, the counts displayed in the tabs (e.g. “In progress”, “Queued”, etc.) were not updating on a poll interval. This has been fixed.

All Changes

https://github.com/dagster-io/dagster/compare/1.0.13...1.0.14

New

• AssetMaterialization now has a metadata property, which allows accessing the materialization’s metadata as a dictionary.
• DagsterInstance now has a get_latest_materialization_event method, which allows fetching the most recent materialization event for a particular asset key.
• RepositoryDefinition.load_asset_value and AssetValueLoader.load_asset_value now work with IO managers whose load_input implementation accesses the op_def and name attributes on the InputContext.
• RepositoryDefinition.load_asset_value and AssetValueLoader.load_asset_value now respect the DAGSTER_HOME environment variable.
• InMemoryIOManager, the IOManager that backs mem_io_manager, has been added to the public API.
• The multi_asset_sensor (experimental) now supports marking individual partitioned materializations as “consumed”. Unconsumed materializations will appear in future calls to partitioned context methods.
• The build_multi_asset_sensor_context testing method (experimental) now contains a flag to set the cursor to the newest events in the Dagster instance.
• TableSchema now has a static constructor that enables building it from a dictionary of column names to column types.
• Added a new CLI command dagster run migrate-repository which lets you migrate the run history for a given job from one repository to another. This is useful to preserve run history for a job when you have renamed a repository, for example.
• [dagit] The run timeline view now shows jobs grouped by repository, with each repository section collapsible. This feature was previously gated by a feature flag, and is now turned on for everyone.
• [dagster-airbyte] Added option to specify custom request params to the Airbyte resource, which can be used for auth purposes.
• [dagster-airbyte] When loading Airbyte assets from an instance or from YAML, a filter function can be specified to ignore certain connections.
• [dagster-airflow] DagsterCloudOperator and DagsterOperator now support Airflow 2. Previously, installing the library on Airflow 2 would break due to an import error.
• [dagster-duckdb] A new integration with DuckDB allows you to store op outputs and assets in an in-process database.

Bugfixes

• Previously, if retries were exceeded when running with execute_in_process, no error would be raised. Now, a DagsterMaxRetriesExceededError will be launched off.
• [dagster-airbyte] Fixed generating assets for Airbyte normalization tables corresponding with nested union types.
• [dagster-dbt] When running assets with load_assets_from_...(..., use_build=True), AssetObservation events would be emitted for each test. These events would have metadata fields which shared names with the fields added to the AssetMaterialization events, causing confusing historical graphs for fields such as Compilation Time. This has been fixed.
• [dagster-dbt] The name for the underlying op for load_assets_from_... was generated in a way which was non-deterministic for dbt projects which pulled in external packages, leading to errors when executing across multiple processes. This has been fixed.

Dependency changes

• [dagster-dbt] The package no longer depends on pandas and dagster-pandas.

Community Contributions

• [dagster-airbyte] Added possibility to change request timeout value when calling Airbyte. Thanks @FransDel!
• [dagster-airflow] Fixed an import error in dagster_airflow.hooks. Thanks @bollwyvl!
• [dagster-gcp] Unpin Google dependencies. dagster-gcp now supports google-api-python-client 2.x. Thanks @amarrella!
• [dagstermill] Fixed an issue where DagsterTranslator was missing an argument required by newer versions of papermill. Thanks @tizz98!

Documentation

• Added an example, underneath examples/assets_smoke_test, that shows how to write a smoke test that feeds empty data to all the transformations in a data pipeline.
• Added documentation for build_asset_reconciliation_sensor.
• Added documentation for monitoring partitioned materializations using the multi_asset_sensor and kicking off subsequent partitioned runs.
• [dagster-cloud] Added documentation for running the Dagster Cloud Docker agent with Docker credential helpers.
• [dagster-dbt] The class methods of the dbt_cli_resource are now visible in the API docs for the dagster-dbt library.
• [dagster-dbt] Added a step-by-step tutorial for using dbt models with Dagster software-defined assets

All Changes

https://github.com/dagster-io/dagster/compare/1.0.12...1.0.13

New

• The multi_asset_sensor (experimental) now accepts an AssetSelection of assets to monitor. There are also minor API updates for the multi-asset sensor context.
• AssetValueLoader, the type returned by RepositoryDefinition.get_asset_value_loader is now part of Dagster’s public API.
• RepositoryDefinition.load_asset_value and AssetValueLoader.load_asset_value now support a partition_key argument.
• RepositoryDefinition.load_asset_value and AssetValueLoader.load_asset_value now work with I/O managers that invoke context.upstream_output.asset_key.
• When running Dagster locally, the default amount of time that the system waits when importing user code has been increased from 60 seconds to 180 seconds, to avoid false positives when importing code with heavy dependencies or large numbers of assets. This timeout can be configured in dagster.yaml as follows:

code_servers:
  local_startup_timeout: 120

• [dagit] The “Status” section has been renamed to “Deployment”, to better reflect that this section of the app shows deployment-wide information.
• [dagit] When viewing the compute logs for a run and choosing a step to filter on, there is now a search input to make it easier to find the step you’re looking for.
• [dagster-aws] The EcsRunLauncher can now launch runs in ECS clusters using both Fargate and EC2 capacity providers. See the Deploying to ECS docs for more information.
• [dagster-airbyte] Added the load_assets_from_airbyte_instance function which automatically generates asset definitions from an Airbyte instance. For more details, see the new Airbyte integration guide.
• [dagster-airflow] Added the DagsterCloudOperator and DagsterOperator , which are airflow operators that enable orchestrating dagster jobs, running on either cloud or OSS dagit instances, from Apache Airflow.

Bugfixes

• Fixed a bug where if resource initialization failed for a dynamic op, causing other dynamic steps to be skipped, those skipped dynamic steps would be ignored when retrying from failure.
• Previously, some invocations within the Dagster framework would result in warnings about deprecated metadata APIs. Now, users should only see warnings if their code uses deprecated metadata APIs.
• How the daemon process manages its understanding of user code artifacts has been reworked to improve memory consumption.
• [dagit] The partition selection UI in the Asset Materialization modal now allows for mouse selection and matches the UI used for partitioned op jobs.
• [dagit] Sidebars in Dagit shrink more gracefully on small screens where headers and labels need to be truncated.
• [dagit] Improved performance for loading runs with >10,000 logs
• [dagster-airbyte] Previously, the port configuration in the airbyte_resource was marked as not required, but if it was not supplied, an error would occur. It is now marked as required.
• [dagster-dbt] A change made to the manifest.json schema in dbt 1.3 would result in an error when using load_assets_from_dbt_project or load_assets_from_manifest_json. This has been fixed.
• [dagster-postgres] connections that fail due to sqlalchemy.exc.TimeoutError now retry

Breaking Changes

• [dagster-aws] The redshift_resource no longer accepts a schema configuration parameter. Previously, this parameter would error whenever used, because Redshift connections do not support this parameter.

Community Contributions

• We now reference the correct method in the "loading asset values outside of Dagster runs" example (thank you Peter A. I. Forsyth!)
• We now reference the correct test directory in the “Create a New Project” documentation (thank you Peter A. I. Forsyth!)
• [dagster-pyspark] dagster-pyspark now contains a LazyPysparkResource that only initializes a spark session once it’s accessed (thank you @zyd14!)

Experimental

• The new build_asset_reconciliation_sensor function accepts a set of software-defined assets and returns a sensor that automatically materializes those assets after their parents are materialized.
• [dagit] A new "groups-only" asset graph feature flag allows you to zoom way out on the global asset graph, collapsing asset groups into smaller nodes you can double-click to expand.

New

• RepositoryDefinition now exposes a load_asset_value method, which accepts an asset key and invokes the asset’s I/O manager’s load_input function to load the asset as a Python object. This can be used in notebooks to do exploratory data analysis on assets.
• Methods to fetch a list of partition keys from an input/output PartitionKeyRange now exist on the op execution context and input/output context.
• [dagit] On the Instance Overview page, batched runs in the run timeline view will now proportionally reflect the status of the runs in the batch instead of reducing all run statuses to a single color.
• [dagster-dbt] [dagster-snowflake] You can now use the Snowflake IO manager with dbt assets, which allows them to be loaded from Snowflake into Pandas DataFrames in downstream steps.
• The dagster package’s pin of the alembic package is now much less restrictive.

Bugfixes

• The sensor daemon when using threads will no longer evaluate the next tick for a sensor if the previous one is still in flight. This resolves a memory leak in the daemon process.
• The scheduler will no longer remove tracked state for automatically running schedules when they are absent due to a workspace load error.
• The way user code severs manage repository definitions has been changed to more efficiently serve requests.
• The @multi_asset decorator now respects its config_schema parameter.
• [dagit] Config supplied to define_asset_job is now prefilled in the modal that pops up when you click the Materialize button on an asset job page, so you can quickly adjust the defaults.
• [dagster-dbt] Previously, DagsterDbtCliErrors produced from the dagster-dbt library would contain large serialized objects representing the raw unparsed logs from the relevant cli command. Now, these messages will contain only the parsed version of these messages.
• Fixed an issue where the deploy_ecs example didn’t work when built and deployed on an M1 Mac.

Community Contributions

• [dagster-fivetran] The resync_parameters configuration on the fivetran_resync_op is now optional, enabling triggering historical re*syncs for connectors. Thanks @dwallace0723!

Documentation

• Improved API documentation for the Snowflake resource.

All Changes

https://github.com/dagster-io/dagster/compare/1.0.10...1.0.11

New

• Run status sensors can now monitor all runs in a Dagster Instance, rather than just runs from jobs within a single repository. You can enable this behavior by setting monitor_all_repositories=True in the run status sensor decorator.
• The run_key argument on RunRequest and run_request_for_partition is now optional.
• [dagster-databricks] A new “verbose_logs” config option on the databricks_pyspark_step_launcher makes it possible to silence non-critical logs from your external steps, which can be helpful for long-running, or highly parallel operations (thanks @zyd14!)
• [dagit] It is now possible to delete a run in Dagit directly from the run page. The option is available in the dropdown menu on the top right of the page.
• [dagit] The run timeline on the Workspace Overview page in Dagit now includes ad hoc asset materialization runs.

Bugfixes

• Fixed a set of bugs in multi_asset_sensor where the cursor would fail to update, and materializations would be returned out of order for latest_materialization_records_by_partition.
• Fixed a bug that caused failures in runs with time-partitioned asset dependencies when the PartitionsDefinition had an offset that wasn’t included in the date format. E.g. a daily-partitioned asset with an hour offset, whose date format was %Y-%m-%d.
• An issue causing code loaded by file path to import repeatedly has been resolved.
• To align with best practices, singleton comparisons throughout the codebase have been converted from (e.g.) foo == None to foo is None (thanks @chrisRedwine!).
• [dagit] In backfill jobs, the “Partition Set” column would sometimes show an internal __ASSET_JOB name, rather than a comprehensible set of asset keys. This has been fixed.
• [dagit] It is now possible to collapse all Asset Observation rows on the AssetDetails page.
• [dagster-dbt] Fixed issue that would cause an error when loading assets from dbt projects in which a source had a “*” character in its name (e.g. BigQuery sharded tables)
• [dagster-k8s] Fixed an issue where the k8s_job_op would sometimes fail if the Kubernetes job that it creates takes a long time to create a pod.
• Fixed an issue where links to the compute logs for a run would sometimes fail to load.
• [dagster-k8s] The k8s_job_executor now uses environment variables in place of CLI arguments to avoid limits on argument size with large dynamic jobs.

Documentation

• Docs added to explain subsetting graph-backed assets. You can use this feature following the documentation here.
• UI updated to reflect separate version schemes for mature core Dagster packages and less mature integration libraries

New

• The multi_asset_sensor (experimental) now has improved capabilities to monitor asset partitions via a latest_materialization_records_by_partition method.
• Performance improvements for the Partitions page in Dagit.

Bugfixes

• Fixed a bug that caused the op_config argument of dagstermill.get_context to be ignored
• Fixed a bug that caused errors when loading the asset details page for assets with time window partitions definitions
• Fixed a bug where assets sometimes didn’t appear in the Asset Catalog while in Folder view.
• [dagit] Opening the asset lineage tab no longer scrolls the page header off screen in some scenarios
• [dagit] The asset lineage tab no longer attempts to materialize source assets included in the upstream / downstream views.
• [dagit] The Instance page Run Timeline no longer commingles runs with the same job name in different repositories
• [dagit] Emitting materializations with JSON metadata that cannot be parsed as JSON no longer crashes the run details page
• [dagit] Viewing the assets related to a run no longer shows the same assets multiple times in some scenarios
• [dagster-k8s] Fixed a bug with timeouts causing errors in k8s_job_op
• [dagster-docker] Fixed a bug with Op retries causing errors with the docker_executor

Community Contributions

• [dagster-aws] Thanks @Vivanov98 for adding the list_objects method to S3FakeSession!

Experimental

• [dagster-airbyte] Added an experimental function to automatically generate Airbyte assets from project YAML files. For more information, see the dagster-airbyte docs.
• [dagster-airbyte] Added the forward_logs option to AirbyteResource, allowing users to disble forwarding of Airbyte logs to the compute log, which can be expensive for long-running syncs.
• [dagster-airbyte] Added the ability to generate Airbyte assets for basic normalization tables generated as part of a sync.

Documentation

• [dagster-dbt] Added a new guide focused on the dbt Cloud integration.
• Fixed a bug that was hiding display of some public methods in the API docs.
• Added documentation for managing full deployments in Dagster Cloud, including a reference for deployment configuration options.

New

• With the new cron_schedule argument to TimeWindowPartitionsDefinition, you can now supply arbitrary cron expressions to define time window-based partition sets.
• Graph-backed assets can now be subsetted for execution via AssetsDefinition.from_graph(my_graph, can_subset=True).
• RunsFilter is now exported in the public API.
• [dagster-k8s] The dagster-user-deployments.deployments[].schedulerName Helm value for specifying custom Kubernetes schedulers will now also apply to run and step workers launched for the given user deployment. Previously it would only apply to the grpc server.

Bugfixes

• In some situations, default asset config was ignored when a subset of assets were selected for execution. This has been fixed.
• Added a pin to grpcio in dagster to address an issue with the recent 0.48.1 grpcio release that was sometimes causing Dagster code servers to hang.
• Fixed an issue where the “Latest run” column on the Instance Status page sometimes displayed an older run instead of the most recent run.

Community Contributions

• In addition to a single cron string, cron_schedule now also accepts a sequence of cron strings. If a sequence is provided, the schedule will run for the union of all execution times for the provided cron strings, e.g., ['45 23 * * 6', '30 9 * * 0] for a schedule that runs at 11:45 PM every Saturday and 9:30 AM every Sunday. Thanks @erinov1!
• Added an optional boolean config install_default_libraries to databricks_pyspark_step_launcher . It allows to run Databricks jobs without installing the default Dagster libraries .Thanks @nvinhphuc!

Experimental

• [dagster-k8s] Added additional configuration fields (container_config, pod_template_spec_metadata, pod_spec_config, job_metadata, and job_spec_config) to the experimental k8s_job_op that can be used to add additional configuration to the Kubernetes pod that is launched within the op.

New

• Several updates to the Dagit run timeline view: your time window preference will now be preserved locally, there is a clearer “Now” label to delineate the current time, and upcoming scheduled ticks will no longer be batched with existing runs.
• [dagster-k8s] ingress.labels is now available in the Helm chart. Any provided labels are appended to the default labels on each object (helm.sh/chart, app.kubernetes.io/version, and app.kubernetes.io/managed-by).
• [dagster-dbt] Added support for two types of dbt nodes: metrics, and ephemeral models
• When constructing a GraphDefinition manually, InputMapping and OutputMapping objects should be directly constructed.
• [dagit] The launchpad tab is no longer shown for Asset jobs. Asset jobs can be launched via the “Materialize All” button shown on the Overview tab. To provide optional configuration, hold shift when clicking “Materialize”.

Bugfixes

• [dagster-snowflake] Pandas is no longer imported when dagster_snowflake is imported. Instead, it’s only imported when using functionality inside dagster-snowflake that depends on pandas.
• Recent changes to run status sensors caused sensors that only monitored jobs in external repositories to also monitor all jobs in the current repository. This has been fixed.
• Fixed an issue where "unhashable type" errors could be spawned from sensor executions.
• [dagit] Clicking between assets in different repositories from asset groups and asset jobs now works as expected.
• [dagit] The DAG rendering of composite ops with more than one input/output mapping has been fixed.
• [dagit] Selecting a source asset in Dagit no longer produces a GraphQL error
• [dagit] Viewing “Related Assets” for an asset run now shows the full set of assets included in the run, regardless of whether they were materialized successfully.
• [dagit] The Asset Lineage view has been simplified and lets you know if the view is being clipped and more distant upstream/downstream assets exist.
• Fixed erroneous experimental warnings being thrown when using with_resources alongside source assets.

Breaking Changes

• The arguments to the (internal) InputMapping and OutputMapping constructors have changed.

Community Contributions

• The ssh_resource can now accept configuration from environment variables. Thanks @cbini!
• Spelling corrections in migrations.md. Thanks @gogi2811!

New

• [dagit] nbconvert is now installed as an extra in Dagit.
• Multiple assets can be monitored for materialization using the multi_asset_sensor (experimental).
• Run status sensors can now monitor jobs in external repositories.
• The config argument of define_asset_job now works if the job contains partitioned assets.
• When configuring sqlite-based storages in dagster.yaml, you can now point to environment variables.
• When emitting RunRequests from sensors, you can now optionally supply an asset_selection argument, which accepts a list of AssetKeys to materialize from the larger job.
• [dagster-dbt] load_assets_from_dbt_project and load_assets_from_dbt_manifest now support the exlude parameter, allowing you to more precisely which resources to load from your dbt project (thanks @flvndh!)

Bugfixes

• Previously, types for multi-assets would display incorrectly in Dagit when specified. This has been fixed.
• In some circumstances, viewing nested asset paths in Dagit could lead to unexpected empty states. This was due to incorrect slicing of the asset list, and has been fixed.
• Fixed an issue in Dagit where the dialog used to wipe materializations displayed broken text for assets with long paths.
• [dagit] Fixed the Job page to change the latest run tag and the related assets to bucket repository-specific jobs. Previously, runs from jobs with the same name in different repositories would be intermingled.
• Previously, if you launched a backfill for a subset of a multi-asset (e.g. dbt assets), all assets would be executed on each run, instead of just the selected ones. This has been fixed.
• [dagster-dbt] Previously, if you configured a select parameter on your dbt_cli_resource , this would not get passed into the corresponding invocations of certain context.resources.dbt.x() commands. This has been fixed.

New

• Assets can now be materialized to storage conditionally by setting output_required=False. If this is set and no result is yielded from the asset, Dagster will not create an asset materialization event, the I/O manager will not be invoked, downstream assets will not be materialized, and asset sensors monitoring the asset will not trigger.
• JobDefinition.run_request_for_partition can now be used inside sensors that target multiple jobs (Thanks Metin Senturk!)
• The environment variable DAGSTER_GRPC_TIMEOUT_SECONDS now allows for overriding the default timeout for communications between host processes like dagit and the daemon and user code servers.
• Import time for the dagster module has been reduced, by approximately 50% in initial measurements.
• AssetIn now accepts a dagster_type argument, for specifying runtime checks on asset input values.
• [dagit] The column names on the Activity tab of the asset details page no longer reference the legacy term “Pipeline”.
• [dagster-snowflake] The execute_query method of the snowflake resource now accepts a use_pandas_result argument, which fetches the result of the query as a Pandas dataframe. (Thanks @swotai!)
• [dagster-shell] Made the execute and execute_script_file utilities in dagster_shell part of the public API (Thanks Fahad Khan!)
• [dagster-dbt] load_assets_from_dbt_project and load_assets_from_dbt_manifest now support the exclude parameter. (Thanks @flvndh!)

Bugfixes

• [dagit] Removed the x-frame-options response header from Dagit, allowing the Dagit UI to be rendered in an iframe.
• [fully-featured project example] Fixed the duckdb IO manager so the comment_stories step can load data successfully.
• [dagster-dbt] Previously, if a select parameter was configured on the dbt_cli_resource, it would not be passed into invocations of context.resources.dbt.run() (and other similar commands). This has been fixed.
• [dagster-ge] An incompatibility between dagster_ge_validation_factory and dagster 1.0 has been fixed.
• [dagstermill] Previously, updated arguments and properties to DagstermillExecutionContext were not exposed. This has since been fixed.

Documentation

• The integrations page on the docs site now has a section for links to community-hosted integrations. The first linked integration is @silentsokolov’s Vault integration.

New

• Failure now has an allow_retries argument, allowing a means to manually bypass retry policies.
• dagstermill.get_context and dagstermill.DagstermillExecutionContext have been updated to reflect stable dagster-1.0 APIs. pipeline/solid referencing arguments / properties will be removed in the next major version bump of dagstermill.
• TimeWindowPartitionsDefinition now exposes a get_cron_schedule method.

Bugfixes

• In some situations where an asset was materialized and that asset that depended on a partitioned asset, and that upstream partitioned asset wasn’t part of the run, the partition-related methods of InputContext returned incorrect values or failed erroneously. This was fixed.
• Schedules and sensors with the same names but in different repositories no longer affect each others idempotence checks.
• In some circumstances, reloading a repository in Dagit could lead to an error that would crash the page. This has been fixed.

Community Contributions

• @will-holley added an optional key argument to GCSFileManager methods to set the GCS blob key, thank you!
• Fix for sensors in fully featured example, thanks @pwachira!

Documentation

• New documentation for getting started with Dagster Cloud, including:
  • Serverless deployment documentation
  • Hybrid deployment documentation

New

• When the workpace is updated, a notification will appear in Dagit, and the Workspace tab will automatically refresh.

Bugfixes

• Restored the correct version mismatch warnings between dagster core and dagster integration libraries
• Field.__init__ has been typed, which resolves an error that pylance would raise about default_value
• Previously, dagster_type_materializer and dagster_type_loader expected functions to take a context argument from an internal dagster import. We’ve added DagsterTypeMaterializerContext and DagsterTypeLoaderContext so that functions annotated with these decorators can annotate their arguments properly.
• Previously, a single-output op with a return description would not pick up the description of the return. This has been rectified.

Community Contributions

• Fixed the dagster_slack documentation examples. Thanks @ssingh13-rms!

Documentation

• New documentation for Dagster Cloud environment variables.
• The full list of APIs removed in 1.0 has been added to the migration guide.

Bugfixes

• Fixed an issue where Dagster libraries would sometimes log warnings about mismatched versions despite having the correct version loaded.

Documentation

• The Dagster Cloud docs now live alongside all the other Dagster docs! Check them out by nagivating to Deployment > Cloud.

Major Changes

• A docs site overhaul! Along with tons of additional content, the existing pages have been significantly edited and reorganized to improve readability.
• All Dagster examplesare revamped with a consistent project layout, descriptive names, and more helpful README files.
• A new dagster projectCLI contains commands for bootstrapping new Dagster projects and repositories
  • dagster project scaffold creates a folder structure with a single Dagster repository and other files such as workspace.yaml. This CLI enables you to quickly start building a new Dagster project with everything set up.
  • dagster project from-example downloads one of the Dagster examples. This CLI helps you to quickly bootstrap your project with an officially maintained example. You can find the available examples via dagster project list-examples.
  • Check out Create a New Project for more details.
• A default_executor_def argument has been added to the @repository decorator. If specified, this will be used for any jobs (asset or op) which do not explicitly set an executor_def.
• A default_logger_defs argument has been added to the @repository decorator, which works in the same way as default_executor_def.
• A new execute_job function presents a Python API for kicking off runs of your jobs.
• Run status sensors may now yield RunRequests, allowing you to kick off a job in response to the status of another job.
• When loading an upstream asset or op output as an input, you can now set custom loading behavior using the input_manager_key argument to AssetIn and In.
• In the UI, the global lineage graph has been brought back and reworked! The graph keeps assets in the same group visually clustered together, and the query bar allows you to visualize a custom slice of your asset graph.

Breaking Changes and Deprecations

Legacy API Removals

In 1.0.0, a large number of previously-deprecated APIs have been fully removed. A full list of breaking changes and deprecations, alongside instructions on how to migrate older code, can be found in MIGRATION.md. At a high level:

• The solid and pipeline APIs have been removed, along with references to them in extension libraries, arguments, and the CLI (deprecated in 0.13.0).
• The AssetGroup and build_asset_job APIs, and a host of deprecated arguments to asset-related functions, have been removed (deprecated in 0.15.0).
• The EventMetadata and EventMetadataEntryData APIs have been removed (deprecated in 0.15.0).

Deprecations

• dagster_type_materializer and DagsterTypeMaterializer have been marked experimental and will likely be removed within a 1.x release. Instead, use an IOManager.
• FileManager and FileHandle have been marked experimental and will likely be removed within a 1.x release.

Other Changes

• As of 1.0.0, Dagster no longer guarantees support for python 3.6. This is in line with PEP 494, which outlines that 3.6 has reached end of life.
• [planned] In an upcoming 1.x release, we plan to make a change that renders values supplied to configured in Dagit. Up through this point, values provided to configured have not been sent anywhere outside the process where they were used. This change will mean that, like other places you can supply configuration, configured is not a good place to put secrets: You should not include any values in configuration that you don't want to be stored in the Dagster database and displayed inside Dagit.
• fs_io_manager, s3_pickle_io_manager, and gcs_pickle_io_manager, and adls_pickle_io_manager no longer write out a file or object when handling an output with the None or Nothing type.
• The custom_path_fs_io_manager has been removed, as its functionality is entirely subsumed by the fs_io_manager, where a custom path can be specified via config.
• The default typing_type of a DagsterType is now typing.Any instead of None.

New since 0.15.8

• [dagster-databricks] When using the databricks_pyspark_step_launcher the events sent back to the host process are now compressed before sending, resulting in significantly better performance for steps which produce a large number of events.
• [dagster-dbt] If an error occurs in load_assets_from_dbt_project while loading your repository, the error message in Dagit will now display additional context from the dbt logs, instead of just DagsterDbtCliFatalRuntimeError.

Bugfixes

• Fixed a bug that causes Dagster to ignore the group_name argument to AssetsDefinition.from_graph when a key_prefix argument is also present.
• Fixed a bug which could cause GraphQL errors in Dagit when loading repositories that contained multiple assets created from the same graph.
• Ops and software-defined assets with the None return type annotation are now given the Nothing type instead of the Any type.
• Fixed a bug that caused AssetsDefinition.from_graph and from_op to fail when invoked on a configured op.
• The materialize function, which is not experimental, no longer emits an experimental warning.
• Fixed a bug where runs from different repositories would be intermingled when viewing the runs for a specific repository-scoped job/schedule/sensor.
• [dagster-dbt] A regression was introduced in 0.15.8 that would cause dbt logs to show up in json format in the UI. This has been fixed.
• [dagster-databricks] Previously, if you were using the databricks_pyspark_step_launcher, and the external step failed to start, a RESOURCE_DOES_NOT_EXIST error would be surfaced, without helpful context. Now, in most cases, the root error causing the step to fail will be surfaced instead.

Documentation

• New guide that walks through seamlessly transitioning code from development to production environments.
• New guide that demonstrates using Branch Deployments to test Dagster code in your cloud environment without impacting your production data.

New

• Software-defined asset config schemas are no longer restricted to dicts.
• The OpDefinition constructor now accept ins and outs arguments, to make direct construction easier.
• define_dagstermill_op accepts ins and outs in order to make direct construction easier.

Bugfixes

• Fixed a bug where default configuration was not applied when assets were selected for materialization in Dagit.
• Fixed a bug where RunRequests returned from run_status_sensors caused the sensor to error.
• When supplying config to define_asset_job, an error would occur when selecting most asset subsets. This has been fixed.
• Fixed an error introduced in 0.15.7 that would prevent viewing the execution plan for a job re-execution from 0.15.0 → 0.15.6
• [dagit] The Dagit server now returns 500 http status codes for GraphQL requests that encountered an unexpected server error.
• [dagit] Fixed a bug that made it impossible to kick off materializations of partitioned asset if the day_offset, hour_offset, or minute_offset parameters were set on the asset’s partitions definition.
• [dagster-k8s] Fixed a bug where overriding the Kubernetes command to use to run a Dagster job by setting the dagster-k8s/config didn’t actually override the command.
• [dagster-datahub] Pinned version of acryl-datahub to avoid build error.

Breaking Changes

• The constructor of JobDefinition objects now accept a config argument, and the preset_defs argument has been removed.

Deprecations

• DagsterPipelineRunMetadataValue has been renamed to DagsterRunMetadataValue. DagsterPipelineRunMetadataValue will be removed in 1.0.

Community Contributions

• Thanks to @hassen-io for fixing a broken link in the docs!

Documentation

• MetadataEntry static methods are now marked as deprecated in the docs.
• PartitionMappings are now included in the API reference.
• A dbt example and memoization example using legacy APIs have been removed from the docs site.

New

• DagsterRun now has a job_name property, which should be used instead of pipeline_name.
• TimeWindowPartitionsDefinition now has a get_partition_keys_in_range method which returns a sequence of all the partition keys between two partition keys.
• OpExecutionContext now has asset_partitions_def_for_output and asset_partitions_def_for_input methods.
• Dagster now errors immediately with an informative message when two AssetsDefinition objects with the same key are provided to the same repository.
• build_output_context now accepts a partition_key argument that can be used when testing the handle_output method of an IO manager.

Bugfixes

• Fixed a bug that made it impossible to load inputs using a DagsterTypeLoader if the InputDefinition had an asset_key set.
• Ops created with the @asset and @multi_asset decorators no longer have a top-level “assets” entry in their config schema. This entry was unused.
• In 0.15.6, a bug was introduced that made it impossible to load repositories if assets that had non-standard metadata attached to them were present. This has been fixed.
• [dagster-dbt] In some cases, using load_assets_from_dbt_manifest with a select parameter that included sources would result in an error. This has been fixed.
• [dagit] Fixed an error where a race condition of a sensor/schedule page load and the sensor/schedule removal caused a GraphQL exception to be raised.
• [dagit] The “Materialize” button no longer changes to “Rematerialize” in some scenarios
• [dagit] The live overlays on asset views, showing latest materialization and run info, now load faster
• [dagit] Typing whitespace into the launchpad Yaml editor no longer causes execution to fail to start
• [dagit] The explorer sidebar no longer displays “mode” label and description for jobs, since modes are deprecated.

Community Contributions

• An error will now be raised if a @repository decorated function expects parameters. Thanks @roeij!

Documentation

• The non-asset version of the Hacker News example, which lived inside examples/hacker_news/, has been removed, because it hadn’t received updates in a long time and had drifted from best practices. The asset version is still there and has an updated README. Check it out here

All Changes

https://github.com/dagster-io/dagster/compare/0.15.6...0.15.7

New

• When an exception is wrapped by another exception and raised within an op, Dagit will now display the full chain of exceptions, instead of stopping after a single exception level.
• A default_logger_defs argument has been added to the @repository decorator. Check out the docs on specifying default loggers to learn more.
• AssetsDefinition.from_graph and AssetsDefinition.from_op now both accept a partition_mappings argument.
• AssetsDefinition.from_graph and AssetsDefinition.from_op now both accept a metadata_by_output_name argument.
• define_asset_job now accepts an executor_def argument.
• Removed package pin for gql in dagster-graphql.
• You can now apply a group name to assets produced with the @multi_asset decorator, either by supplying a group_name argument (which will apply to all of the output assets), or by setting the group_name argument on individual AssetOuts.
• InputContext and OutputContext now each have an asset_partitions_def property, which returns the PartitionsDefinition of the asset that’s being loaded or stored.
• build_schedule_from_partitioned_job now raises a more informative error when provided a non-partitioned asset job
• PartitionMapping, IdentityPartitionMapping, AllPartitionMapping, and LastPartitionMapping are exposed at the top-level dagster package. They're currently marked experimental.
• When a non-partitioned asset depends on a partitioned asset, you can now control which partitions of the upstream asset are used by the downstream asset, by supplying a PartitionMapping.
• You can now set PartitionMappings on AssetIn.
• [dagit] Made performance improvements to the loading of the partitions and backfill pages.
• [dagit] The Global Asset Graph is back by popular demand, and can be reached via a new “View global asset lineage ”link on asset group and asset catalog pages! The global graph keeps asset in the same group visually clustered together and the query bar allows you to visualize a custom slice of your asset graph.
• [dagit] Simplified the Content Security Policy and removed frame-ancestors restriction.
• [dagster-dbt] load_assets_from_dbt_project and load_assets_from_dbt_manifest now support a node_info_to_group_name_fn parameter, allowing you to customize which group Dagster will assign each dbt asset to.
• [dagster-dbt] When you supply a runtime_metadata_fn when loading dbt assets, this metadata is added to the default metadata that dagster-dbt generates, rather than replacing it entirely.
• [dagster-dbt] When you load dbt assets with use_build_command=True, seeds and snapshots will now be represented as Dagster assets. Previously, only models would be loaded as assets.

Bugfixes

• Fixed an issue where runs that were launched using the DockerRunLauncher would sometimes use Dagit’s Python environment as the entrypoint to launch the run, even if that environment did not exist in the container.
• Dagster no longer raises a “Duplicate definition found” error when a schedule definition targets a partitioned asset job.
• Silenced some erroneous warnings that arose when using software-defined assets.
• When returning multiple outputs as a tuple, empty list values no longer cause unexpected exceptions.
• [dagit] Fixed an issue with graph-backed assets causing a GraphQL error when graph inputs were type-annotated.
• [dagit] Fixed an issue where attempting to materialize graph-backed assets caused a graphql error.
• [dagit] Fixed an issue where partitions could not be selected when materializing partitioned assets with associated resources.
• [dagit] Attempting to materialize assets with required resources now only presents the launchpad modal if at least one resource defines a config schema.

Breaking Changes

• An op with a non-optional DynamicOutput will now error if no outputs are returned or yielded for that dynamic output.
• If an Output object is used to type annotate the return of an op, an Output object must be returned or an error will result.

Community Contributions

• Dagit now displays the path of the output handled by PickledObjectS3IOManager in run logs and Asset view. Thanks @danielgafni

Documentation

• The Hacker News example now uses stable 0.15+ asset APIs, instead of the deprecated 0.14.x asset APIs.
• Fixed the build command in the instructions for contributing docs changes.
• [dagster-dbt] The dagster-dbt integration guide now contains information on using dbt with Software-Defined Assets.

All Changes

https://github.com/dagster-io/dagster/compare/0.15.5...0.15.6

New

• Added documentation and helm chart configuration for threaded sensor evaluations.
• Added documentation and helm chart configuration for tick retention policies.
• Added descriptions for default config schema. Fields like execution, loggers, ops, and resources are now documented.
• UnresolvedAssetJob objects can now be passed to run status sensors.
• [dagit] A new global asset lineage view, linked from the Asset Catalog and Asset Group pages, allows you to view a graph of assets in all loaded asset groups and filter by query selector and repo.
• [dagit] A new option on Asset Lineage pages allows you to choose how many layers of the upstream / downstream graph to display.
• [dagit] Dagit's DAG view now collapses large sets of edges between the same ops for improved readability and rendering performance.

Bugfixes

• Fixed a bug with materialize that would cause required resources to not be applied correctly.
• Fixed issue that caused repositories to fail to load when build_schedule_from_partitioned_job and define_asset_job were used together.
• Fixed a bug that caused auto run retries to always use the FROM_FAILURE strategy
• Previously, it was possible to construct Software-Defined Assets from graphs whose leaf ops were not mapped to assets. This is invalid, as these ops are not required for the production of any assets, and would cause confusing behavior or errors on execution. This will now result in an error at definition time, as intended.
• Fixed issue where the run monitoring daemon could mark completed runs as failed if they transitioned quickly between STARTING and SUCCESS status.
• Fixed stability issues with the sensor daemon introduced in 0.15.3 that caused the daemon to fail heartbeat checks if the sensor evaluation took too long.
• Fixed issues with the thread pool implementation of the sensor daemon where race conditions caused the sensor to fire more frequently than the minimum interval.
• Fixed an issue with storage implementations using MySQL server version 5.6 which caused SQL syntax exceptions to surface when rendering the Instance overview pages in Dagit.
• Fixed a bug with the default_executor_def argument on repository where asset jobs that defined executor config would result in errors.
• Fixed a bug where an erroneous exception would be raised if an empty list was returned for a list output of an op.
• [dagit] Clicking the "Materialize" button for assets with configurable resources will now present the asset launchpad.
• [dagit] If you have an asset group and no jobs, Dagit will display it by default rather than directing you to the asset catalog.
• [dagit] DAG renderings of software-defined assets now display only the last component of the asset's key for improved readability.
• [dagit] Fixes a regression where clicking on a source asset would trigger a GraphQL error.
• [dagit] Fixed issue where the “Unloadable” section on the sensors / schedules pages in Dagit were populated erroneously with loadable sensors and schedules
• [dagster-dbt] Fixed an issue where an exception would be raised when using the dbt build command with Software-Defined Assets if a test was defined on a source.

Deprecations

• Removed the deprecated dagster-daemon health-check CLI command

Community Contributions

• TimeWindow is now exported from the dagster package (Thanks @nvinhphuc!)
• Added a fix to allow customization of slack messages (Thanks @solarisa21!)
• [dagster-databricks] The databricks_pyspark_step_launcher now allows you to configure the following (Thanks @Phazure!):
  • the aws_attributes of the cluster that will be spun up for the step.
  • arbitrary environment variables to be copied over to databricks from the host machine, rather than requiring these variables to be stored as secrets.
  • job and cluster permissions, allowing users to view the completed runs through the databricks console, even if they’re kicked off by a service account.

Experimental

• [dagster-k8s] Added k8s_job_op to launch a Kubernetes Job with an arbitrary image and CLI command. This is in contrast with the k8s_job_executor, which runs each Dagster op in a Dagster job in its own k8s job. This op may be useful when you need to orchestrate a command that isn't a Dagster op (or isn't written in Python). Usage:

  from dagster_k8s import k8s_job_op
  
  my_k8s_op = k8s_job_op.configured({
   "image": "busybox",
   "command": ["/bin/sh", "-c"],
   "args": ["echo HELLO"],
   },
   name="my_k8s_op",
  )
  

• [dagster-dbt] The dbt asset-loading functions now support partitions_def and partition_key_to_vars_fn parameters, adding preliminary support for partitioned dbt assets. To learn more, check out the Github issue!

All Changes

https://github.com/dagster-io/dagster/compare/0.15.4...0.15.5

Bugfixes

• Reverted sensor threadpool changes from 0.15.3 to address daemon stability issues.

All Changes

https://github.com/dagster-io/dagster/compare/0.15.3...0.15.4