search

dagster-io / dagster

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

Deployment Ops overview inconsistent source asset naming compared to asset #20732

Open ion-elgreco opened 6 months ago

ion-elgreco commented 6 months ago

Dagster version

1.6.10

What's the issue?

We use key prefixes in all our assets/source_assets. In the deployment overview of Ops we can see assets Ops are nicely showed without the long prefix, but source_assets are shown with this prefix, see example below:

image

First row is an asset, second row is a source-asset.

What did you expect to happen?

Only display the asset name of the source-asset Op instead of also showing the key prefix.

How to reproduce?

Create source asset with key-prefix and loo at the Ops overview UI.

Deployment type

None

Deployment details

No response

Additional information

No response

Message from the maintainers

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

bengotow commented 6 months ago

Hey @ion-elgreco thanks for filing this, it sounds like dagster is generating op names differently for assets and source assets? For assets, the key prefix is ignored, and for source assets, the prefix is incorporated into the op name?

Going to pass this to our foundations team to review.