Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AssetDefinition.from_op() - Resulting Name ambiguous #28118

Open
michimussato opened this issue Feb 28, 2025 · 0 comments
Open

AssetDefinition.from_op() - Resulting Name ambiguous #28118

michimussato opened this issue Feb 28, 2025 · 0 comments
Labels
type: bug Something isn't working

Comments

@michimussato
Copy link
Contributor

michimussato commented Feb 28, 2025

What's the issue?

The resulting name of the asset produced by AssetDefinition.from_op() is based on the op name suffixed by an increment. This results in a messy representation in the UI and it can be hard to find the right one:

Image

What did you expect to happen?

It would be beneficial to be able to specify a name attribute as it can be done with the asset decorator:

@asset(
    name="MyAssetName"
)
def not_my_asset_name():
    return True

As a good step in the right direction, it would already help if the key_prefix of the AssetDefinition.from_op() gets prepended as a prefix to the resulting asset in the UI.

How to reproduce?

Create multiple assets based on the same op using AssetDefinition.from_op()

Dagster version

1.9.11

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.

@michimussato michimussato added the type: bug Something isn't working label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant