Field.__init__ has been typed, which resolves an error that pylance would raise about default_valuedagster_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.dagster_slack documentation examples. Thanks @ssingh13-rms!dagster project CLI 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.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.default_logger_defs argument has been added to the @repository decorator, which works in the same way as default_executor_def.execute_job function presents a Python API for kicking off runs of your jobs.RunRequests, allowing you to kick off a job in response to the status of another job.input_manager_key argument to AssetIn and In.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:
solid and pipeline APIs have been removed, along with references to them in extension libraries, arguments, and the CLI (deprecated in 0.13.0).AssetGroup and build_asset_job APIs, and a host of deprecated arguments to asset-related functions, have been removed (deprecated in 0.15.0).EventMetadata and EventMetadataEntryData APIs have been removed (deprecated in 0.15.0).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.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.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.typing_type of a DagsterType is now typing.Any instead of None.pip install dagster=={DAGSTER_VERSION} dagster-somelibrary=={DAGSTER_VERSION}
this should be converted to:
pip install dagster=={DAGSTER_VERSION} dagster-somelibrary
to make sure the correct library version is installed.
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.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.group_name argument to AssetsDefinition.from_graph when a key_prefix argument is also present.None return type annotation are now given the Nothing type instead of the Any type.AssetsDefinition.from_graph and from_op to fail when invoked on a configured op.materialize function, which is not experimental, no longer emits an experimental warning.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.dicts.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.RunRequests returned from run_status_sensors caused the sensor to error.define_asset_job, an error would occur when selecting most asset subsets. This has been fixed.500 http status codes for GraphQL requests that encountered an unexpected server error.day_offset, hour_offset, or minute_offset parameters were set on the asset’s partitions definition.dagster-k8s/config didn’t actually override the command.acryl-datahub to avoid build error.JobDefinition objects now accept a config argument, and the preset_defs argument has been removed.DagsterPipelineRunMetadataValue has been renamed to DagsterRunMetadataValue. DagsterPipelineRunMetadataValue will be removed in 1.0.MetadataEntry static methods are now marked as deprecated in the docs.PartitionMappings are now included in the API reference.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.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.asset_key set.@asset and @multi_asset decorators no longer have a top-level “assets” entry in their config schema. This entry was unused.load_assets_from_dbt_manifest with a select parameter that included sources would result in an error. This has been fixed.@repository decorated function expects parameters. Thanks @roeij!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