search

dagster-io / dagster

An orchestration platform for the development, production, and observation of data assets.
https://dagster.io
Apache License 2.0
11.51k stars 1.45k forks source link

One or more of the selected assets are defined in multiple code locations. Rename these assets to avoid collisions and then try again. #18534

Open ndellosa95 opened 10 months ago

ndellosa95 commented 10 months ago

Dagster version

1.5.10

What's the issue?

You get this error message if you have multiple definitions of an asset with the same asset key in different code locations and you try and run the asset on the launchpad. However, if you have a schedule for the asset job and you enable it, it runs fine.

What did you expect to happen?

I would expect consistent behavior - either this should be allowed or it should not work in all cases.

How to reproduce?

Run dagster with two code locations and an asset with same asset key defined in both.

Deployment type

Dagster Helm chart

Deployment details

No response

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.

ytoast commented 7 months ago

I am facing the same issue, did you manage to resolve this?