🚨 Breaking Changes 🚨:
PR #68 includes the following breaking changes:
- The
active_volumesource (and accompanyingstg_fivetran_log__active_volumemodel) has been deprecated from the Fivetran Log connector. In its place, theincremental_martable (and accompanyingstg_fivetran_log__incremental_marmodel) has been added. This new source has been swapped within the package to reference the new source table.- This new source table has enriched data behind the paid and free MAR across Fivetran connectors within your destinations.
- Removed the
monthly_active_rowsfield from thefivetran_log__mar_table_historyandfivetran_log__usage_mar_destination_historymodels. In it's place the following fields have been added:free_mothly_active_rows: Detailing the total free MARpaid_mothly_active_rows: Detailing the total paid MARtotal_mothly_active_rows: Detailing the total free and paid MAR
PR #64 includes the following breaking changes:
- Dispatch update for dbt-utils to dbt-core cross-db macros migration. Specifically
{{ dbt_utils.<macro> }}have been updated to{{ dbt.<macro> }}for the below macros:any_valuebool_orcast_bool_to_textconcatdate_truncdateadddatediffescape_single_quotesexcepthashintersectlast_daylengthlistaggpositionreplacerightsafe_castsplit_partstring_literaltype_biginttype_floattype_inttype_numerictype_stringtype_timestamparray_appendarray_concatarray_construct
- For
current_timestampandcurrent_timestamp_in_utcmacros, the dispatch AND the macro names have been updated to the below, respectively:dbt.current_timestamp_backcompatdbt.current_timestamp_in_utc_backcompat
dbt_utils.surrogate_keyhas also been updated todbt_utils.generate_surrogate_key. Since the method for creating surrogate keys differ, we suggest all users do afull-refreshfor the most accurate data. For more information, please refer to dbt-utils release notes for this update.packages.ymlhas been updated to reflect new defaultfivetran/fivetran_utilsversion, previously[">=0.3.0", "<0.4.0"]now[">=0.4.0", "<0.5.0"].