You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the "Events" tab of the asset details page, each event has a "Source data" section which contains links to upstream materializations that the event is based on.
These links are populated using a heuristic that can be inaccurate and also deviate from the materialization lineage information that we include in asset event tags.
The heuristic: look at the timestamp of the event and find the latest materialization of the upstream asset that's before that timestamp. One way this can be inaccurate is if the upstream asset was re-materialized after the downstream asset started the process of being materialized.
Events have a tag prefixed with "input_event_pointer" that encodes Dagster's best understanding of the upstream event they're derived from.
The text was updated successfully, but these errors were encountered:
On the "Events" tab of the asset details page, each event has a "Source data" section which contains links to upstream materializations that the event is based on.
These links are populated using a heuristic that can be inaccurate and also deviate from the materialization lineage information that we include in asset event tags.
The heuristic: look at the timestamp of the event and find the latest materialization of the upstream asset that's before that timestamp. One way this can be inaccurate is if the upstream asset was re-materialized after the downstream asset started the process of being materialized.
Events have a tag prefixed with "input_event_pointer" that encodes Dagster's best understanding of the upstream event they're derived from.
The text was updated successfully, but these errors were encountered: