When I create a non-partitioned asset and open the run config it is not partitioned (as expected)
When I subsequently create a partitioned asset, and open the run config for the original non-partitioned asset, the run config is now partitioned.
What did you expect to happen?
I expect that the run configuration for the non-partitioned asset remains non-partitioned. And the run config for the partitioned asset to be partitioned. I don't expect all the assets to be partitioned.
How to reproduce?
Create a definitions.py file with the code below, run dagster dev -f definitions.py:
Observe in the UI the my_asset is now partitioned even though it hasn't changed.
If I attempt to materialise without specifying a partition, I get a warning
Now if I add another partitioned asset (using a different PartitionDefinition), the partition drop-down is correct for the run configuration on both of the partitioned asset, but the non-partitioned asset now uses the new PartitionDefinition
Dagster version
1.6.1 (also observed in 1.5.13)
What's the issue?
When I create a non-partitioned asset and open the run config it is not partitioned (as expected)
When I subsequently create a partitioned asset, and open the run config for the original non-partitioned asset, the run config is now partitioned.
What did you expect to happen?
I expect that the run configuration for the non-partitioned asset remains non-partitioned. And the run config for the partitioned asset to be partitioned. I don't expect all the assets to be partitioned.
How to reproduce?
Create a
definitions.py
file with the code below, rundagster dev -f definitions.py
:In the UI, open the launchpad and observe the asset is not partitioned.
Now, add a partitioned asset:
Observe in the UI the
my_asset
is now partitioned even though it hasn't changed.If I attempt to materialise without specifying a partition, I get a warning
Now if I add another partitioned asset (using a different
PartitionDefinition
), the partition drop-down is correct for the run configuration on both of the partitioned asset, but the non-partitioned asset now uses the newPartitionDefinition
Deployment type
Dagster Helm chart
Deployment details
Kubernetes deployment, though this is reproducible locally
Additional information
No response
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.