fix(dagster): Update dagster (patch) #131
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==0.19.13
->==0.19.14
==0.19.13
->==0.19.14
1.3.13
->1.3.14
Release Notes
dagster-io/dagster (dagster-azure)
v0.19.14
New
DynamicPartitionsDefinition
andSensorResult
are no longer marked experimentalDagsterInstance
now has aget_status_by_partition
method, which returns the status of each partition for a given asset. Thanks renzhe-brian!DagsterInstance
now has aget_latest_materialization_code_versions
method, which returns the code version of the latest materialization for each of the provided (non-partitioned) assets.build_asset_context
has been added as an asset focused replacement forbuild_op_context
.build_op_context
now accepts apartition_key_range
parameter.AssetSelection.upstream_source_assets
method allows selecting source assets upstream of the current selection.AssetSelection.key_prefixes
andAssetSelection.groups
now accept an optionalinclude_sources
parameter.DbtCli
resource is no longer marked experimental.global_config
parameter of theDbtCli
resource has been renamed toglobal_config_flags
load_assets_from_dbt_project
andload_assets_from_dbt_manifest
now work with theDbtCli
resource.manifest
argument of the@dbt_assets
decorator now additionally can accept aPath
argument representing a path to the manifest file or dictionary argument representing the raw manifest blob.DbtCli.cli
from inside a@dbt_assets
-decorated function, you no longer need to supply the manifest argument as long as you provide the context argument.DbtManifest
object can now generate schedules using dbt selection syntax.DbtCli.cli
and the underlying command fails, an exception will now be raised. To suppress the exception, run theDbtCli.cli(..., raise_on_error=False
).Bugfixes
OutputContext
when usingwith_attributes
orAssetsDefinition.from_graph
.max_materializations_per_minute
parameter, those older partitions would not be properly discarded from consideration on subsequent ticks. This has been fixed.from __future__ import annotations
) would cause errors in most cases when used with Dagster definitions. This has been fixed for the vast majority of cases.AssetExecutionContext
has returned to being a type alias forOpExecutionContext
.Breaking Changes
time_window_partition_scope_minutes
parameter of theAutoMaterializePolicy
class has been removed. Instead,max_materializations_per_minute
should be used to limit the number of runs that may be kicked off for a partitioned asset.Deprecations
DbtCliResource
has been deprecated in favor ofDbtCli
.dagit
has been deprecated in favor of a new packagedagster-webserver
.OpExecutionContext.asset_partition_key_range
has been deprecated in favor ofpartition_key_range
.Community Contributions
databricks_pyspark_step_launcher
will no longer error when executing steps that target a single partition of aDynamicPartitionsDefinition
(thanks @weberdavid!).Experimental
@observable_source_asset
decorator now accepts anauto_observe_interval_minutes
parameter. If the asset daemon is turned on, then the observation function will automatically be run at this interval.DbtCliTask
has been renamed toDbtCliInvocation
get_asset_key_by_output_name
andget_node_info_by_output_name
methods ofDbtManifest
have been renamed toget_asset_key_for_output_name
andget_node_info_for_output_name
, respectively.Documentation
DagsterInstance
,*MetadataValue
,DagsterType
, and others.dagster-pandera
now has an API docs page.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.