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
The collect_freshness is a macro used to ensure that the source freshness test doesn't fail for cases when a Fivetran dbt package has disabled a source. Previously, if a source was disabled in a package, the freshness test would still fail. This macro ensured that it would not fail.
However, in the recent versions of dbt-core there is now a native feature (see example here) which allows sources to be enabled/disabled based on a tag. Therefore, this macro will no longer be necessary once we move to the v0.5.0 release of fivetran_utils and only support dbt-core versions of v1.8.0 or greater.
Once we move to v0.5.0 of Fivetran Utils and update all Fivetran dbt packages to support this version, we will fully remove the collect_freshness macro from the fivetran_utils dbt package.
The text was updated successfully, but these errors were encountered:
fivetran-joemarkiewicz
changed the title
[FEATURE] - Deprecate collect_freshness macro
[FEATURE] - Deprecate collect_freshness macro in v0.5.0 release
Jul 10, 2024
The collect_freshness is a macro used to ensure that the source freshness test doesn't fail for cases when a Fivetran dbt package has disabled a source. Previously, if a source was disabled in a package, the freshness test would still fail. This macro ensured that it would not fail.
However, in the recent versions of dbt-core there is now a native feature (see example here) which allows sources to be enabled/disabled based on a tag. Therefore, this macro will no longer be necessary once we move to the v0.5.0 release of fivetran_utils and only support dbt-core versions of v1.8.0 or greater.
Once we move to v0.5.0 of Fivetran Utils and update all Fivetran dbt packages to support this version, we will fully remove the collect_freshness macro from the fivetran_utils dbt package.
The text was updated successfully, but these errors were encountered: