Breaking Changes
--env
flag no longer works for the pipeline launch
or pipeline execute
commands. Use --config
instead.pipeline execute
command no longer accepts the --workspace
argument.
To execute pipelines in a workspace, use pipeline launch
instead.New
ResourceDefinition.mock_resource
helper for magic mocking resources. Example usage can be found hererow_count
metadata entry from the Dask DataFrame type check (thanks @kinghuang!)orient
to the config options when materializing a Dask DataFrame to json
(thanks @kinghuang!)Bugfixes
configured
to a solid definition would overwrite inputs from run config.Bugfixes
dagster-k8s-celery
executor when executing solid subsetsBreaking Changes
IntermediateStore
API. IntermediateStorage
now wraps an ObjectStore, and TypeStoragePlugin
now accepts an IntermediateStorage
instance instead of an IntermediateStore
instance. (Noe that IntermediateStore
and IntermediateStorage
are both internal APIs that are used in some non-core libraries).Breaking Changes
dagit
key is no longer part of the instance configuration schema and must be removed from dagster.yaml
files before they can be used.-d
can no longer be used as a command-line argument to specify a mode. Use --mode
instead.--preset
instead of --preset-name
to specify a preset to the pipeline launch
command.config
argument to the ConfigMapping
, @composite_solid
, @solid
, SolidDefinition
, @executor
, ExecutorDefinition
, @logger
, LoggerDefinition
, @resource
, and ResourceDefinition
APIs, which we deprecated in 0.8.0. Use config_schema
instead.New
-d
or --working-directory
can be used to specify a working directory in any command that
takes in a -f
or --python_file
argument.create_dagster_pandas_dataframe_type
. This is the currently
supported API for custom pandas data frame type creation.configured
API for predefining configuration for various definitions: https://legacy-docs.dagster.io/overview/configuration/#configuredBreaking Changes
AssetMaterializations
no longer accepts a dagster_type
argument. This reverts the change
billed as "AssetMaterializations
can now have type information attached as metadata." in the
previous release.New
AssetMaterializations
can now have type information attached as metadata. See the materializations tutorial for moreBugfixes
context['ts']
was not passed properlytask_acks_late: true
that resulted in a 409 Conflict error
from Kubernetes. The creation of a Kubernetes Job will now be aborted if another Job with the same name existsDocs