asOf URL parameter, which shows a snapshot of the asset at the provided timestamp, including parent materializations as of that time.make dev_install has been fixed.reload_repository_location and submit_pipeline_execution have been fixed - the underlying GraphQL queries had a missing inline fragment case.@solid decorator can now wrap a function without a context argument, if no context information is required. For example, you can now do:@solid def basic_solid(): return 5 @solid def solid_with_inputs(x, y): return x + y
however, if your solid requires config or resources, then you will receive an error at definition time.
metadata_entries argument may now instead accept a metadata argument, which should allow for a more convenient API. The metadata argument takes a dictionary with string labels as keys and EventMetadata values. Some base types (str, int, float, and JSON-serializable list/dicts) are also accepted as values and will be automatically coerced to the appropriate EventMetadata value. For example:@solid def old_metadata_entries_solid(df): yield AssetMaterialization( "my_asset", metadata_entries=[ EventMetadataEntry.text("users_table", "table name"), EventMetadataEntry.int(len(df), "row count"), EventMetadataEntry.url("http://mysite/users_table", "data url") ] ) @solid def new_metadata_solid(df): yield AssetMaterialization( "my_asset", metadata={ "table name": "users_table", "row count": len(df), "data url": EventMetadata.url("http://mysite/users_table") } )
--heartbeat-tolerance argument that allows you to configure how long the process can run before shutting itself down due to a hanging thread. This parameter can be used to troubleshoot failures with the daemon process.PartitionSetDefinition.create_schedule_definition, the partition_selector function that determines which partition to use for a given schedule tick can now return a list of partitions or a single partition, allowing you to create schedules that create multiple runs for each schedule tick.KeyError.Dict and Set types for solid inputs/outputs now works as expected. Previously a structure like Dict[str, Dict[str, Dict[str, SomeClass]]] could result in confusing errors.solid_config.map and collect steps downstream of other map and collect steps to mysteriously not execute when using multiprocess executors has been resolved.solid_exception on HookContext which returns the actual exception object thrown in a failed solid. See the example “Accessing failure information in a failure hook“ for more details.solid_output_values on HookContext which returns the computed output values.make_values_resource helper for defining a resource that passes in user-defined values. This is useful when you want multiple solids to share values. See the example for more details.--path-prefix, our color-coded favicons denoting the success or failure of a run were not loading properly. This has been fixed.DagsterInstance.get() no longer falls back to an ephemeral instance if DAGSTER_HOME is not set. We don’t expect this to break normal workflows. This change allows our tooling to be more consistent around it’s expectations. If you were relying on getting an ephemeral instance you can use DagsterInstance.ephemeral() directly.HookContext have been removed. step_key and mode_def have been documented as attributes.config_schema for all configurable objects - solids, resources, IO managers, composite solids, executors, loggers - is now Any. This means that you can now use configuration without explicitly providing a config_schema. Refer to the docs for more details: https://docs.dagster.io/concepts/configuration/config-schema.input_defs and output_defs on @solid will now flexibly combine data that can be inferred from the function signature that is not declared explicitly via InputDefinition / OutputDefinition. This allows for more concise defining of solids with reduced repetition of information.dagster-daemon process within the last 5 minutes. Previously, it would only display errors from the last 30 seconds.dagster-daemon process.DockerRunLauncher now accepts a container_kwargs config parameter, allowing you to specify any argument to the run container that can be passed into the Docker containers.run method. See https://docker-py.readthedocs.io/en/stable/containers.html#docker.models.containers.ContainerCollection.run for the full list of available options.celery_k8s_job_executor now accepts a job_wait_timeout allowing you to override the default of 24 hours.--prefix-path argument.Requested state.output_config_schema or input_config_schema arguments of @io_manager, the config would still be required. Now, the config is not required.Assets catalog, where the view switcher would flip back from the directory view to the flat view when navigating into subdirectories.dagster-daemon process would crash if it experienced a transient connection error while connecting to the Dagster database.dagster-airflow scaffold command would raise an exception if a preset was specified.ModeDefinition that are not required by a pipeline no longer require runtime configuration. This should make it easier to share modes or resources among multiple pipelines.RetryRequested is yielded from a notebook using dagstermill.yield_event.--path-prefix option, leading to failed GraphQL requests and broken pages. This bug was introduced in 0.11.4, and is now fixed.update_timestamp column in the runs table is now updated with a UTC timezone, making it consistent with the create_timestamp column.dagster-pandas on pandas. You can now include any version of pandas. (https://github.com/dagster-io/dagster/issues/3350)requests in dagster. Now only dagit depends on requests.pyrsistent in dagster.