Improved error handling when the intermediate storage stores and retrieves objects.
New URL scheme in Dagit, with repository details included on all paths for pipelines, solids, and schedules
Relaxed constraints for the AssetKey constructor, to enable arbitrary strings as part of the key path.
When executing a subset of a pipeline, configuration that does not apply to the current subset but would be valid in the original pipeline is now allowed and ignored.
GCSComputeLogManager was added, allowing for compute logs to be persisted to Google cloud storage
The step-partition matrix in Dagit now auto-reloads runs
Bugfixes
Dagit bugfixes and improvements
When specifying a namespace during helm install, the same namespace will now be used by the K8sScheduler or K8sRunLauncher, unless overridden.
@pipeline decorated functions with -> None typing no longer cause unexpected problems.
Fixed an issue where compute logs might not always be complete on Windows.
CliApiRunLauncher and GrpcRunLauncher have been combined into DefaultRunLauncher.
If you had one of these run launchers in your dagster.yaml, replace it with DefaultRunLauncher
or remove the run_launcher: section entirely.
New
Added a type loader for typed dictionaries: can now load typed dictionaries from config.
Bugfixes
Dagit bugfixes and improvements
Added error handling for repository errors on startup and reload
Repaired timezone offsets
Fixed pipeline explorer state for empty pipelines
Fixed Scheduler table
User-defined k8s config in the pipeline run tags (with key dagster-k8s/config) will now be
passed to the k8s jobs when using the dagster-k8s and dagster-celery-k8s run launchers.
Previously, only user-defined k8s config in the pipeline definition’s tag was passed down.
Experimental
Run queuing: the new QueuedRunCoordinator enables limiting the number of concurrent runs.
The DefaultRunCoordinator launches jobs directly from Dagit, preserving existing behavior.
[dagster-dask] Allow connecting to an existing scheduler via its address
[dagster-aws] Importing dagster_aws.emr no longer transitively importing dagster_spark
[dagster-dbr] CLI solids now emit materializations
Community contributions
Docs fix (Thanks @kaplanbora!)
Bug fixes
PipelineDefinition 's that do not meet resource requirements for its types will now fail at definition time
Dagit bugfixes and improvements
Fixed an issue where a run could be left hanging if there was a failure during launch
Deprecated
We now warn if you return anything from a function decorated with @pipeline. This return value actually had no impact at all and was ignored, but we are making changes that will use that value in the future. By changing your code to not return anything now you will avoid any breaking changes with zero user-visible impact.
Removed DagsterKubernetesPodOperator in dagster-airflow.
Removed the execute_plan mutation from dagster-graphql.
ModeDefinition, PartitionSetDefinition, PresetDefinition, @repository, @pipeline, and ScheduleDefinition names must pass the regular expression r"^[A-Za-z0-9_]+$" and not be python keywords or disallowed names. See DISALLOWED_NAMES in dagster.core.definitions.utils for exhaustive list of illegal names.
dagster-slack is now upgraded to use slackclient 2.x - this means that this resource will only support Python 3.6 and above.
[K8s] Added a health check to the helm chart for user deployments, which relies on a new dagster api grpc-health-check cli command present in Dagster 0.9.16 and later.
New
Add helm chart configurations to allow users to configure a K8sRunLauncher, in place of the CeleryK8sRunLauncher.
“Copy URL” button to preserve filter state on Run page in dagit
Community Contributions
Dagster CLI options can now be passed in via environment variables (Thanks @xinbinhuang!)
New --limit flag on the dagster run list command (Thanks @haydarai!)
Bugfixes
Addressed performance issues loading the /assets table in dagit. Requires a data migration to create a secondary index by running dagster instance reindex.