- Corrected references to connectors and connections in the README. (#19)
PR #14 includes the following breaking changes:
- This update is made breaking due to the following changes in the Linkedin Company Pages Fivetran Connector.
- Deprecated source table
ugc_post_share_content_media
- Added source table
post_content
- See the May 2023 release notes for full details.
- Deprecated source table
- Removed the following deprecated columns from
stg_linkedin_pages__ugc_post_history
:deleted_actor
deleted_timestamp
specific_content_primary_landing_page_url
specific_content_share_commentary_attributes
specific_content_share_commentary_inferred_locale
specific_content_share_commentary_text
specific_content_share_media_category
target_audience_targeted_entities
version_tag
- Added the following new column to
stg_linkedin_pages__ugc_post_history
:commentary
- Added source table
post_content
and staging tablestg_linkedin_pages__post_content
- Updated documentation with the updated columns.
- Updated seeds to reflect the above changes.
PR #12 includes the following updates:
- Incorporated the new
fivetran_utils.drop_schemas_automation
macro into the end of each Buildkite integration test job. - Updated the pull request templates.
PR #10 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
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"]
.
- Modified the
ugc_post_id
parsing logic withinstg_linkedin_pages__organization_ugc_post
to dynamically parse the correctugc_post_id
. Previously, only posts of theshare
type where being parsed correctly. This will now work for bothshare
andugcpost
types (#6)
- @bthomson22 (#7)
Previously, Redshift threw the error "constant expressions are not supported in partition by clauses" for the model int_linkedin_pages__latest_post_history
.
To resolve this, linkedin_pages_source models will be materialized as tables rather than views in dbt_project.yml
. (#4)
The original release! This package contains staging models, designed to work simultaneously with our LinkedIn 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 organization table's ID column is renamed
organization_id
.