dbt Freshness Check Fails w/ KeyError Due to "Missing" Metadata about dagster HOT 4 CLOSED

Hey there - the underlying issue here is that we expect that metadata field to be provided on observations in order to determine the timestamp to compute freshness against. I would check to see whether this information is being provided on your timestamps.

The rough error experience here should be fixed going forward by #22486 (should be going out in 1.7.11), which will disregard observations without a timestamp rather than attempt to retrieve the metadata always.

from dagster.

Thanks for the quick response, @dpeng817. It looks like the timestamp is being provided by the dagster-dbt integration. I'll upgrade to 1.7.11 this week when the release happens to see if that fixes this.

from dagster.

I think we only yield observations for dbt tests on sources; I think that when a dbt asset "completes", it should be yielding a materialization, not an observation. Which makes me think that the upgrade to 1.7.11 will fix this for you. But would be nice to confirm that that's what you're seeing (ie, observations for dbt tests, and materializations otherwise)

@camcyr-at-brzwy

from dagster.

@dpeng817 - The upgrade to v1.7.12 fixed this issue for me. Thanks for the help!

from dagster.