In the /assets/example?view=events view of an asset, dagster/row_count is filtered out of the metadata, but it does not appear in another place in the UI.
What did you expect to happen?
Either the row_count metadata shouldn’t be filtered in this view (easiest), or there should be a dedicated UI treatment for it in this view.
How to reproduce?
With this test file, run with dagster dev -f thisfile.py
Materialize the asset twice, then go to http://127.0.0.1:3000/assets/example. You can see the row count right underneath status (it's "promoted" to a dedicated UI treatment), and the someotherdata in the metadata section.
But if you go to http://127.0.0.1:3000/assets/example?view=events , you can still see someotherdata in metadata, but dagster/row_count neither appears in metadata nor in a dedicated treatment.
So if you're using this view to look back in time to see how row count has changed over materializations, there's no way to do so.
Dagster version
dagster, version 1.8.9
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.
By submitting this issue, you agree to follow Dagster's Code of Conduct.
What's the issue?
In the
/assets/example?view=events
view of an asset,dagster/row_count
is filtered out of the metadata, but it does not appear in another place in the UI.What did you expect to happen?
Either the row_count metadata shouldn’t be filtered in this view (easiest), or there should be a dedicated UI treatment for it in this view.
How to reproduce?
With this test file, run with
dagster dev -f thisfile.py
Materialize the asset twice, then go to http://127.0.0.1:3000/assets/example. You can see the row count right underneath status (it's "promoted" to a dedicated UI treatment), and the someotherdata in the metadata section.
But if you go to http://127.0.0.1:3000/assets/example?view=events , you can still see
someotherdata
in metadata, butdagster/row_count
neither appears in metadata nor in a dedicated treatment.So if you're using this view to look back in time to see how row count has changed over materializations, there's no way to do so.
Dagster version
dagster, version 1.8.9
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. By submitting this issue, you agree to follow Dagster's Code of Conduct.