AutomationCondition.eager(), AutomationCondition.missing(), and AutomationCondition.on_cron conditions are now compatible with asset checks.AssetSelection.materializable(), which returns only assets that are materializable in an existing selection.AutomationCondition.all_deps_blocking_checks_passed condition, which can be used to prevent materialization when any upstream blocking checks have failed.code_version parameter to the @graph_asset decorator.LaunchPartitionBackfill mutation is submitted to GQL with invalid partition keys, it will now return an early PartitionKeysNotFoundError.AssetSelection.checks_for_assets now accepts AssetKeys and string asset keys, in addition to AssetsDefinitions.get_objects now has a since_last_modified that enables only fetching objects modified after a given timestamp.dagster_aws.pipes.PipesEMRCLient ) for running and monitoring AWS EMR jobs from Dagster.AutomationConditions that operate over dependencies.DatabricksPySparkStepLauncher, so that permissions are now set correctly for non-admin users.fetch_column_metadata did not work properly for models imported through dbt dependencies.DagsterK8sPipesClient.run now shows up in API docs.create_pull_request method on GithubClient that enables creating a pull request.create_ref method on GithubClient that enables creating a new branch.dlt.run(...).fetch_row_count() for both partitioned and non-partitioned assets. Thanks @kristianandre!PartitionedConfig objects can now return a RunConfig without causing a crash.AssetIn.__new__ typing for the dagster_type argument.fetch_row_count() method now works for databases returning uppercase column names. Thanks @kristianandre!GCSFileManager.read operations. Thanks @ollie-bell!JobDefinition, @job, and define_asset_job now take a run_tags parameter. If run_tags are defined, they will be attached to all runs of the job, and tags will not be. If run_tags is not set, then tags are attached to all runs of the job (status quo behavior). This change enables the separation of definition-level and run-level tags on jobs.DAGSTER_COMPUTE_LOG_TAIL_WAIT_AFTER_FINISH can now be used to pause before capturing logs (thanks @HynekBlaha!)kinds parameter is now available on AssetSpec.OutputContext now exposes the AssetSpec of the asset that is being stored as an output (thanks, @marijncv!)AutomationCondition on an asset, the label of this condition will now be shown in the sidebar on the Asset Details page.dagster definitions validate have been added.AssetSpec now has a with_io_manager_key method that returns an AssetSpec with the appropriate metadata entry to dictate the key for the IO manager used to load it. The deprecation warning for SourceAsset now references this method.max_runtime_seconds configuration option to run monitoring, allowing you to specify that any run in your Dagster deployment should terminate if it exceeds a certain runtime. Prevoiusly, jobs had to be individually tagged with a dagster/max_runtime tag in order to take advantage of this feature. Jobs and runs can still be tagged in order to override this value for an individual run.tags and a custom execution_fn on a ScheduleDefinition. Schedule tags are intended to annotate the definition and can be used to search and filter in the UI. They will not be attached to run requests emitted from the schedule if a custom execution_fn is provided. If no custom execution_fn is provided, then for back-compatibility the tags will also be automatically attached to run requests emitted from the schedule.SensorDefinition and all of its variants/decorators now accept a tags parameter. The tags annotate the definition and can be used to search and filter in the UI.dagster definitions validate command to Dagster CLI. This command validates if Dagster definitions are loadable.build_op_context in a unit test would sometimes raise a TypeError: signal handler must be signal.SIG_IGN, signal.SIG_DFL, or a callable object Exception on process shutdown.DefaultScheduleStatus.STOPPED / DefaultSensorStatus.STOPPED after performing a reset.--partition-range option to dagster asset materialize CLI. This option only works for assets with single-run Backfill Policies..without() method to AutomationCondition.eager(), AutomationCondition.on_cron(), and AutomationCondition.on_missing() which allows sub-conditions to be removed, e.g. AutomationCondition.eager().without(AutomationCondition.in_latest_time_window()).AutomationCondition.on_missing(), which materializes an asset partition as soon as all of its parent partitions are filled in.pyproject.toml can now load multiple Python modules as individual Code Locations. Thanks, @bdart!ADLS2PickleIOManager now accepts lease_duration configuration. Thanks, @0xfabioo!sling.replicate(...).fetch_row_count().AutomationCondition.any_downstream_condition() with downstream AutoMaterializePolicy objects.process_config_and_initialize did not properly handle processing nested resource config.DepConditionWrapperCondition instead of the key that they were evaluated against.wait_for_pod check now waits until all pods are available, rather than erroneously returning after the first pod becomes available. Thanks @easontm!AssetSpec constructor now raises an error if an invalid group name is provided, instead of an error being raised when constructing the Definitions object.dagster/relation_identifier metadata is now automatically attached to assets which are stored using a DbIOManager.DbtCliResource, the project_dir argument will now override the DBT_PROJECT_DIR environment variable if it exists in the local environment (thanks, @marijncv!).rows_loaded metadata (thanks, @kristianandre!).asset_selection=[] on RunRequest objects yielded from sensors using asset_selection would select all assets instead of none.assets_dbt_python example.database field set (thanks, @dargmuesli!)dbt.adapters.duckdb module when loading dbt assets without that package installed.DagsterInstance.wipe_asset_partitions.allow_missing_partitions as metadata on a downstream asset.object has no attribute '_base_path' error.statuses filter argument to the sensorsOrError GraphQL field was sometimes ignored when querying GraphQL for multiple sensors at the same time.CapturedLogManager and ComputeLogManager APIs into a single base class.PipesECSClient to allow Dagster to interface with ECS tasks.dbt subprocess to wait 25 seconds for the subprocess to cleanly terminate. Previously, it would only wait 2 seconds.sdf subprocess to wait 25 seconds for the subprocess to cleanly terminate. Previously, it would only wait 2 seconds.AutomationCondition using DagsterDltTranslator.get_automation_condition() (Thanks, aksestok!)dagsterDaemon.runRetries.retryOnAssetOrOpFailure to False in the Dagster Helm chart to prevent op retries and run retries from simultaneously firing on the same failure.recursive parameter (Thanks, chrishiste!)dagster/image label when image is provided from user_defined_k8s_config. (Thanks, @HynekBlaha!)custom_user_agent, was provided by defaultPipesGlueClient.run have been deprecated and will be removed in 1.9.0. The new params argument should be used instead.allow_missing_partitions configuration option.PartitionsDefinitions, there will no longer be an implicit asset job __ASSET_JOB_... for each PartitionsDefinition; there will just be one with all the assets. This reduces the time it takes to load code locations with assets with many different PartitionsDefinitions.OpenAIResource (Thanks, @chasleslr!)MultiPartitionMapping with @dbt_assets (Thanks, @arookieds!)AzureBlobComputeLogManager without a secret_key (Thanks, @ion-elgreco and @HynekBlaha!)AutomationCondition and associated static constructors.PipesCloudWatchMessageReaderbuild_op_context and build_asset_context now accepts a run_tags argument.Definitions.RUN_CANCELED events now display relevant error messages.PipesCloudWatchMessageReader can consume logs from CloudWatch as pipes messages.AzureBlobComputeLogManager now supports service principals, thanks @ion-elgreco!dagster-databricks now supports databricks-sdk<=0.17.0.dagster-datahub now allows pydantic versions below 3.0.0, thanks @kevin-longe-unmind!DagsterDbtTranslator class now supports a modfiying the AutomationCondition for dbt models by overriding get_automation_condition.dagster-pandera now supports polars.replicate(...).fetch_column_metadata() method.OpenAIResource now supports organization, project and base_url for configurting the OpenAI client, thanks @chasleslr!numpy<2, thanks @judahrand!AirbyteCloudResource now supports client_id and client_secret for authentication - the api_key approach is no longer supported. This is motivated by the deprecation of portal.airbyte.com on August 15, 2024.databricks-cli and databricks_apiSlingSourceConnection, SlingTargetConnectionSlingSourceConnection, SlingTargetConnectionbuild_sling_assets, and syncAssetSpec objects to the assets argument of Definitions, to let Dagster know about assets without associated materialization functions. This replaces the experimental external_assets_from_specs API, as well as SourceAssets, which are now deprecated. Unlike SourceAssets, AssetSpecs can be used for non-materializable assets with dependencies on Dagster assets, such as BI dashboards that live downstream of warehouse tables that are orchestrated by Dagster. [docs].Definitions objects together into a single larger Definitions object, using the new Definitions.merge API (doc). This makes it easier to structure large Dagster projects, as you can construct a Definitions object for each sub-domain and then merge them together at the top level.BackfillPolicys assigned to assets are now respected for backfills launched from jobs that target those assets.AutomationConditions to your assets to have them automatically executed in response to specific conditions (docs). These serve as a drop-in replacement and improvement over the AutoMaterializePolicy system, which is being marked as deprecated.target parameter, instead of needing to construct a job.Experimental navigation feature flag in user settings.build_metadata_bounds_checks API [doc] enables easily defining asset checks that fail if a numeric asset metadata value falls outside given bounds.PipesSubprocessClient) and its integrations with Lambda (PipesLambdaClient), Kubernetes (PipesK8sClient), and Databricks (PipesDatabricksClient) are no longer experimental.DbtProject class (docs) makes it simpler to define dbt assets that can be constructed in both development and production. DbtProject.prepare_if_dev() eliminates boilerplate for local development, and the dagster-dbt project prepare-and-package CLI can helps pull deps and generate the manifest at build time.dagster-looker package can be used to define a set of Dagster assets from a Looker project that is defined in LookML and is backed by git. See the GitHub discussion for more details.The target of both schedules and sensors can now be set using an experimental target parameter that accepts an AssetSelection or list of assets. Any assets passed this way will also be included automatically in the assets list of the containing Definitions object.
ScheduleDefinition and SensorDefinition now have a target argument that can accept an AssetSelection.
You can now wipe materializations for individual asset partitions.
AssetSpec now has a partitions_def attribute. All the AssetSpecs provided to a @multi_asset must have the same partitions_def.
The assets argument on materialize now accepts AssetSpecs.
The assets argument on Definitions now accepts AssetSpecs.
The new merge method on Definitions enables combining multiple Definitions object into a single larger Definitions object with their combined contents.
Runs requested through the Declarative Automation system now have a dagster/from_automation_condition: true tag applied to them.
Changed the run tags query to be more performant. Thanks @egordm!
Dagster Pipes and its integrations with Lambda, Kubernetes, and Databricks are no longer experimental.
The Definitions constructor will no longer raise errors when the provided definitions aren’t mutually resolve-able – e.g. when there are conflicting definitions with the same name, unsatisfied resource dependencies, etc. These errors will still be raised at code location load time. The new Definitions.validate_loadable static method also allows performing the validation steps that used to occur in constructor.
AssetsDefinitions object provided to a Definitions object will now be deduped by reference equality. That is, the following will now work:
from dagster import asset, Definitions @asset def my_asset(): ... defs = Definitions(assets=[my_asset, my_asset]) # Deduped into just one AssetsDefinition.
[dagster-embedded-elt] Adds translator options for dlt integration to override auto materialize policy, group name, owners, and tags
[dagster-sdf] Introducing the dagster-sdf integration for data modeling and transformations powered by sdf.
[dagster-dbt] Added a new with_insights() method which can be used to more easily attach Dagster+ Insights metrics to dbt executions: dbt.cli(...).stream().with_insights()
build_asset_with_blocking_check has been removed. Use the blocking argument on @asset_check instead.mypy and pydantic 1 may now experience a “metaclass conflict” error when using Config. Previously this would occur when using pydantic 2.AutoMaterializeSensorDefinition has been renamed AutomationConditionSensorDefinition.ComputeLogManager have been removed. Custom ComputeLogManager implementations must also implement the CapturedLogManager interface. This will not affect any of the core implementations available in the core dagster package or the library packages.AutomationConditionSensorDefinition with the name “default_automation_condition_sensor” will be constructed for each code location, and will handle evaluating and launching runs for all AutomationConditions and AutoMaterializePolicies within that code location. You can restore the previous behavior by setting:in your dagster.yaml file.auto_materialize: use_sensors: False
dbt-core==1.6.* has been removed because the version is now end-of-life.KeyPrefixDagsterDbtTranslator has been removed. To modify the asset keys for a set of dbt assets, implementDagsterDbtTranslator.get_asset_key() instead.+meta.dagster_freshness_policy has been removed. Use +meta.dagster.freshness_policy instead.+meta.dagster_auto_materialize_policy has been removed. Use +meta.dagster.auto_materialize_policy instead.load_assets_from_dbt_project, load_assets_from_dbt_manifest, and dbt_cli_resource has been removed. Use @dbt_assets, DbtCliResource, and DbtProject instead to define how to load dbt assets from a dbt project and to execute them.dbt_run_op, dbt_compile_op, etc has been removed. Use @op and DbtCliResource directly to execute dbt commands in an op.AssetExecutionContext , OpExecutionContext , and ScheduleExecutionContext that include datetimes now return standard Python datetime objects instead of Pendulum datetimes. The types in the public API for these properties have always been datetime and this change should not be breaking in the majority of cases, but Pendulum datetimes include some additional methods that are not present on standard Python datetimes, and any code that was using those methods will need to be updated to either no longer use those methods or transform the datetime into a Pendulum datetime. See the 1.8 migration guide for more information and examples.MemoizableIOManager, VersionStrategy, SourceHashVersionStrategy, OpVersionContext, ResourceVersionContext, and MEMOIZED_RUN_TAG, which have been deprecated and experimental since pre-1.0, have been removed.external_assets_from_specs API has been deprecated. Instead, you can directly pass AssetSpec objects to the assets argument of the Definitions constructor.AutoMaterializePolicy has been marked as deprecated in favor of AutomationCondition , which provides a significantly more flexible and customizable interface for expressing when an asset should be executed. More details on how to migrate your AutoMaterializePolicies can be found in the Migration Guide.SourceAsset has been deprecated. See the major changes section and migration guide for more details.asset_partition_key_for_output, asset_partition_keys_for_output, and asset_partition_key_range_for_output, and asset_partitions_time_window_for_output methods on OpExecutionContext have been deprecated. Instead, use the corresponding property: partition_key, partition_keys, partition_key_range, or partition_time_window.partitions_def parameter on define_asset_job is now deprecated. The partitions_def for an asset job is determined from the partitions_def attributes on the assets it targets, so this parameter is redundant.create_shell_command_op and create_shell_script_op have been marked as deprecated in favor of PipesSubprocessClient (see details in Dagster Pipes subprocess reference)load_assets_from_airbyte_project is now deprecated, because the Octavia CLI that it relies on is an experimental feature that is no longer supported. Use build_airbyte_assets or load_assets_from_airbyte_project instead.MonthlyPartitionsDefinition. Thanks @zero_stroke!dagster_aws.per_step_k8s_config configuration option to the celery_k8s_job_executor , allowing the k8s configuration of individual steps to be configured at run launch time. Thanks @alekseik1!log_column_level_metadata macro in favor of the new with_column_metadata API.load_assets_from_airbyte_project as the Octavia CLI has been deprecated.RunRequest(...) as NoneEcsRunLauncher would sometimes fail to launch runs when the include_sidecars option was set to True.total_byte_billed or total_slot_ms in the BigQuery INFORMATION_SCHEMA.JOBS table.ShellCommandBlueprint, you can now use slashes as a delimiter to generate an AssetKey with multiple path components.mlflow_run_id attribute (Thanks Joe Percivall!)dagster dev was logging unexpectedly without the grpcio<1.65.0 pin.ContextVar was created in a different context error was raised when executing an async asset.multi_asset type-checker fix from @aksestok, thanks!