PR #11 includes the following changes:
- This change is made breaking since columns have been removed, since these columns have been removed in the Feb 2024 and Apr 2024 Fivetran Facebook Pages connector updates. You will need to adjust your downstream use cases accordingly.
- Columns removed from staging model
stg_facebook_pages__daily_page_metrics_total
:consumptions
content_activity
engaged_users
places_checkin_mobile
views_external_referrals
views_logged_in_total
views_logout
- Columns removed from staging model
stg_facebook_pages__lifetime_post_metrics_total
:impressions_fan_paid
- Columns removed from staging model
- Updated documentation to reflect the current schema.
- Incorporated the new
fivetran_utils.drop_schemas_automation
macro into the end of each Buildkite integration test job. - Updated the pull request templates.
- Included auto-releaser GitHub Actions workflow to automate future releases.
PR #7 includes the following changes:
- Ensures
actions_post_reactions_total
is not null by falling back to summing the separatepage_actions_post_reactions_*_total
fields (resolves issue #8)
PR #5 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
- Dependencies on
fivetran/fivetran_utils
have been upgraded, previously[">=0.3.0", "<0.4.0"]
now[">=0.4.0", "<0.5.0"]
.
The original release! This package contains staging models, designed to work simultaneously with our Facebook Pages modeling package and our Social Media Reporting package. The staging models name columns consistently across all packages:
- Boolean fields are prefixed with
is_
orhas_
- Timestamps are appended with
_timestamp
- ID primary keys are prefixed with the name of the table. For example, the post table's ID column is renamed
post_id
.