Open mikealfare opened 6 months ago
After discussing internally, we determined that this was a known and acceptable risk. However, we also determined that the documentation should have been updated to reflect this scenario, but was not. We will resolve this by noting the scenario in our docs.
The docs issue will be attached here once I created it. In short, the assumption is that there should be minimal occasions where LAST_ALTERED
reflects something other than a data update. And when it does reflect something other than a data update, that situation would resolve itself with the next data update. The impact is only material if the underlying data is rarely updated. It would seem in those scenarios that the data refresh timestamp is less useful anyway.
Is this a new bug in dbt-snowflake?
Current Behavior
Per @tjirab's https://github.com/dbt-labs/dbt-snowflake/issues/785#issuecomment-1900357214:
Expected Behavior
We would expect to only reflect data updates, and not all object updates, when reporting data freshness.
Steps To Reproduce
Relevant log output
No response
Environment
Additional Context
No response