Open the4thamigo-uk opened 1 month ago
If you change the implementation of the partitioned asset spec from:
class AssetSpecWithPartitionsDef(
namedtuple(
'AssetSpecWithPartitionsDef',
(*dagster.AssetSpec._fields, 'partitions_def'),
defaults=(None,) * (1 + len(dagster.AssetSpec._fields)),
),
):
'''Add partition to AssetSpec (external asset).'''
__slots__ = ()
to:
class AssetSpecWithPartitionsDef(
namedtuple(
'AssetSpecWithPartitionsDef',
(*dagster.AssetSpec._fields, 'auto_materialize_policy'),
defaults=(None,) * (1 + len(dagster.AssetSpec._fields)),
),
):
'''Add partition to AssetSpec (external asset).'''
__slots__ = ()
Then it should work - just ran into this myself
as of:
python -m pip list | grep -e "dagster"
dagster 1.8.4
dagster-dask 0.24.4
dagster-graphql 1.8.4
dagster-pipes 1.8.4
dagster-postgres 0.24.4
dagster-slack 0.24.4
dagster-webserver 1.8.4
Dagster version
1.7.14
What's the issue?
This appears to be related to the workaround for partitioned external assets suggested in this post https://github.com/dagster-io/dagster/discussions/18211.
It looks like this is a problem caused by:
https://github.com/dagster-io/dagster/blame/master/python_modules/dagster/dagster/_core/definitions/asset_spec.py#L131
We are currently using this workaround, and hit this error on startup.
What did you expect to happen?
dagit should startup cleanly
How to reproduce?
Create a partitioned external asset using the workaround detailed in the linked discussion, and start dagit locally.
Deployment type
Local
Deployment details
No response
Additional information
No response
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.