Skip to content

Latest commit

 

History

History
132 lines (113 loc) · 8.4 KB

CHANGELOG.md

File metadata and controls

132 lines (113 loc) · 8.4 KB
Raw

dbt_social_media_reporting v0.5.0

Upstream Breaking Changes (Twitter Organic)

PR #12 from the upstream dbt_twitter_organic_source package includes the following breaking change updates:

  • The source defined in the src_twitter_organic.yml file has been renamed from twitter_organic to twitter to align with the default schema name used by the upstream Fivetran connector.
    • If you're referencing sources from the upstream Twitter Organic packages, please update your source references as needed. See below for the full scope of source changes.
New Source Reference Old Source Reference
"{{ source('twitter','account_history') }}" "{{ source('twitter_organic','account_history') }}"
"{{ source('twitter','organic_tweet_report') }}" "{{ source('twitter_organic','organic_tweet_report') }}"
"{{ source('twitter','tweet') }}" "{{ source('twitter_organic','tweet') }}"
"{{ source('twitter','twitter_user_history') }}" "{{ source('twitter_organic','twitter_user_history') }}"
  • The default schema name has been modified from twitter_organic to now be twitter to more closely align with the default schema name generated by the Fivetran connector. Please be aware if you were leveraging the previous default schema then you will need to update the twitter_organic_schema variable accordingly.
  • All identifier variables in the src_twitter_organic.yml file have been renamed. If you’re using any of these in your project, please update them accordingly. The changes include:
    • Prepending twitter_organic_* has been updated to twitter_* to align with the schema change.
    • The spelling of *_identifer has been corrected to *_identifier.
New Identifier Variable Name Old Identifier Variable Name
twitter_account_history_identifier twitter_organic_account_history_identifer
twitter_organic_tweet_report_identifier twitter_organic_organic_tweet_report_identifer
twitter_tweet_identifier twitter_organic_tweet_identifer
twitter_twitter_user_history_identifier twitter_organic_twitter_user_history_identifer

Under the Hood

  • Consistency validation for integration tests has been added for the social_media_reporting__rollup_report model. (PR #11)
  • Updated the maintainer PR, Issue, Feature Request, and Config templates to resemble the most up to date format. (PR #11)
  • Renamed the Twitter Organic seed files to allow for more testing functionality. (PR #11)
  • Addition of a section tag within the README so the model descriptions may be accessible within the Fivetran UI for Quickstart. (PR #10)

dbt_social_media_reporting v0.4.0

PR #8 includes the following breaking changes:

🚨 Breaking Changes 🚨:

  • This change is made breaking due to changes made in the dbt_facebook_pages_source and dbt_facebook_pages packages. Columns have been removed in the source package (see the dbt_facebook_pages_source v0.3.0 CHANGELOG for more details).
    • No columns were changed in the end models in this package, however if you use the Facebook Pages staging models independently, you will need to update 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

Documentation Update

  • Updated documentation to reflect the current schema.

Under the Hood:

  • Updated the pull request templates.
  • Included auto-releaser GitHub Actions workflow to automate future releases.

dbt_social_media_reporting v0.3.0

PR #7 includes the following breaking changes:

🚨 Breaking Changes 🚨:

Features

  • In social_media_reporting__linkedin_posts_reporting:
    • removed deprecated columns:
      • title_text
      • specific_content_share_commentary_text
    • replaced with new columns:
      • post_title
      • commentary
  • Added source identifiers to give users more dynamic flexibility. Please see this section of the README for more details.
  • Updated README documentation to most current format.

Under the Hood:

  • Updated seeds to reflect the above changes.

PR #6 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.

dbt_social_media_reporting v0.2.0

🚨 Breaking Changes 🚨:

PR #4 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 and current_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"].

dbt_social_media_reporting v0.1.0

The original release! This dbt package aggregates and models data from multiple Fivetran social media connectors. The package standardizes the schemas from the various social media connectors and creates a single reporting model for all activity. It enables you to analyze your post performance via clicks, impressions, shares, likes and comments.

Currently, this package supports the following social media connector types:

NOTE: You do not need to have all of these connector types to use this package, though you should have at least two.