dbt_fivetran_log v0.7.0
fivetran-sheringuyen
released this
04 Jan 14:54
·
258 commits
to main
since this release
🚨 Breaking Changes 🚨:
PR #68 includes the following breaking changes:
- The
active_volume
source (and accompanyingstg_fivetran_log__active_volume
model) has been deprecated from the Fivetran Log connector. In its place, theincremental_mar
table (and accompanyingstg_fivetran_log__incremental_mar
model) 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_rows
field from thefivetran_log__mar_table_history
andfivetran_log__usage_mar_destination_history
models. 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_value
bool_or
cast_bool_to_text
concat
date_trunc
dateadd
datediff
escape_single_quotes
except
hash
intersect
last_day
length
listagg
position
replace
right
safe_cast
split_part
string_literal
type_bigint
type_float
type_int
type_numeric
type_string
type_timestamp
array_append
array_concat
array_construct
- For
current_timestamp
andcurrent_timestamp_in_utc
macros, the dispatch AND the macro names have been updated to the below, respectively:dbt.current_timestamp_backcompat
dbt.current_timestamp_in_utc_backcompat
dbt_utils.surrogate_key
has also been updated todbt_utils.generate_surrogate_key
. Since the method for creating surrogate keys differ, we suggest all users do afull-refresh
for the most accurate data. For more information, please refer to dbt-utils release notes for this update.packages.yml
has been updated to reflect new defaultfivetran/fivetran_utils
version, previously[">=0.3.0", "<0.4.0"]
now[">=0.4.0", "<0.5.0"]
.