Skip to content

Latest commit

 

History

History
123 lines (104 loc) · 7.73 KB

CHANGELOG.md

File metadata and controls

123 lines (104 loc) · 7.73 KB

dbt_google_play_source v0.4.0

PR #14 includes the following updates:

🚨 Breaking Changes 🚨

  • Updated the source identifier format for consistency with other packages and for compatibility with the fivetran_utils.union_data macro. The identifier variables now are:
previous current
stats_installs_app_version_identifier google_play_stats_installs_app_version_identifier
stats_crashes_app_version_identifier google_play_stats_crashes_app_version_identifier
stats_ratings_app_version_identifier google_play_stats_ratings_app_version_identifier
stats_installs_device_identifier google_play_stats_installs_device_identifier
stats_ratings_device_identifier google_play_stats_ratings_device_identifier
stats_installs_os_version_identifier google_play_stats_installs_os_version_identifier
stats_ratings_os_version_identifier google_play_stats_ratings_os_version_identifier
stats_crashes_os_version_identifier google_play_stats_crashes_os_version_identifier
stats_installs_country_identifier google_play_stats_installs_country_identifier
stats_ratings_country_identifier google_play_stats_ratings_country_identifier
stats_store_performance_country_identifier google_play_stats_store_performance_country_identifier
stats_store_performance_traffic_source_identifier google_play_stats_store_performance_traffic_source_identifier
stats_installs_overview_identifier google_play_stats_installs_overview_identifier
stats_crashes_overview_identifier google_play_stats_crashes_overview_identifier
stats_ratings_overview_identifier google_play_stats_ratings_overview_identifier
earnings_identifier google_play_earnings_identifier
financial_stats_subscriptions_country_identifier google_play_financial_stats_subscriptions_country_identifier
  • If you are using the previous identifier, be sure to update to the current version!

Feature update 🎉

  • Unioning capability! This adds the ability to union source data from multiple google_play connectors. Refer to the README for more details.
  • Added a source_relation column in each staging model for tracking the source of each record.
  • Updated tests to account for the new source_relation column.
  • Added casting to staging columns that are used in any downstream COALESCEs, UNIONs, or JOINs to prevent datatype conflicts.
    • Metric fields, such as crashes, *_installs, *_subscriptions, etc., are now cast as the datatype determined by the dbt.type_bigint() macro for your warehouse.

Under the hood 🚘

  • Updated tmp models to union source data using the fivetran_utils.union_data macro.
  • Applied the fivetran_utils.source_relation macro in each staging model to determine the source_relation.
  • Updated src_apple_store.yml to use the current method to enable/disable sources.
  • Included auto-releaser GitHub Actions workflow to automate future releases.

dbt_google_play_source v0.3.1

PR #12 includes the following updates:

🪲 Bug fixes:

  • Updated staging models to cast date_day columns to the date datatype. This prevents downstream datatype conflicts when joining on these columns.

Contributors

dbt_google_play_source v0.3.0

🚨 Breaking Changes 🚨:

PR #11 includes the following changes:

  • Updated the country code mapping table to align with Apple's format and inclusion list of country names. This was change was made in parallel with the Apple App Store dbt package in order to maintain parity for proper aggregating in the combo App Reporting package.
    • This is a 🚨breaking change🚨 as you will need to re-seed (dbt seed --full-refresh) the google_play__country_codes file again.

Under the Hood:

  • Documented the google_play__country_codes seed file in yml (PR #11).
  • Incorporated the new fivetran_utils.drop_schemas_automation macro into the end of each Buildkite integration test job (PR #10).
  • Updated the pull request templates (PR #10).

dbt_google_play_source v0.2.0

🚨 Breaking Changes 🚨:

PR #9 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
  • dbt_utils.surrogate_key has also been updated to dbt_utils.generate_surrogate_key. Since the method for creating surrogate keys differ, we suggest all users do a full-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 default fivetran/fivetran_utils version, previously [">=0.3.0", "<0.4.0"] now [">=0.4.0", "<0.5.0"].

dbt_google_play_source v0.1.1

Fixes

  • Fix casting issue with daily_average_rating (#8)

Contributors

dbt_google_play_source v0.1.0

Initial Release

This is the initial release of this package.

What does this dbt package do?

  • Cleans, tests, and prepares your Google Play data from Fivetran's connector for analysis.
  • Generates a comprehensive data dictionary of your Google Play data via the dbt docs site
  • Materializes staging tables which leverage data in the format described here and is intended to work simultaneously with our Google Play modeling package
    • Refer to our Docs site for more details about these materialized models.

References

For more information refer to the README.