Problemsby IbisTrouble with Dagster asset
Data engineering3 posts from 3 people3d active+11 post in the last 7 days, 0 the 7 days before (steady)
Posts per day
The posts behind it
3, newest firstAge-based retention for `asset_check_executions`### What's the use case? Nothing ever deletes rows from `asset_check_executions`: - `delete_run` does not touch it. `delete_events_for_run` removes the run's `event_logs` and `asset_event_tags` rows only, so a check row outlives its run. - There is no retention setting for it,...dagster-io/dagster · idonadlerOpen ↗compute_logical_data_version joins components with no delimiter, so a compensating upstream change leaves the downstream asset reported FRESH...that "re-execute-from-failure pairs each stored step to the step that produced it" by failing a job, swapping what two identically-named ops return, and re-executing from failure. Pairing is by **step key**, never by position, and a rename or removal makes the key absent rather...dagster-io/dagster · vasilisnasopoulos1 repliesOpen ↗Asset daemon: `execution_failed()` on unpartitioned assets issues one un-batched query per asset per tick...So the per-asset planned-materialization lookup is already recognized as a bottleneck worth engineering around - `execution_failed()` just has no equivalent escape hatch on any storage. Proposed fix: 1. Add a batched storage API, e.g....dagster-io/dagster · jukiewiczm-marketer5 repliesOpen ↗
Companies and products named
About this problem
Evidence
3 posts from 3 people in 1 place, about 1 a week over 51 days. Mostly on dagster-io/dagster. Tools named alongside: PostgreSQL, Kubernetes, SQLite.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts about Dagster with no known issue, sharing the word "asset". First post Sep 1, 2026, latest Oct 21, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
Other Dagster problems
History
Trouble with Dagster asset (3 posts)