fivetran/dbt_fivetran_log v1.0.0

v1.0.0 dbt_fivetran_log

on GitHub

The Fivetran Log connector has been renamed to the "Fivetran Platform" connector. To align with this name change, this package is largely being renamed from fivetran_log to fivetran_platform. This is a very breaking change! 🚨 🚨 🚨 🚨

Bottom Line: What you need to update and/or know:

• If you are setting any variables for this package in your dbt_project.yml, update the name of the prefix of the variable(s) from fivetran_log_* to fivetran_platform_*. The default values for variables have not changed.
• Similarly, any references to package models will need to be updated. The prefix of package models has been updated from fivetran_log__* to fivetran_platform__*.
• If you are overriding the fivetran_log source, you will need to update the overrides property to match the new source name (fivetran_platform).
• Run a full refresh, as we have updated the incremental strategies across warehouses.
• The default build schema suffixes have been changed from _stg_fivetran_log and _fivetran_log to _stg_fivetran_platform and _fivetran_platform respectively. We recommend dropping the old schemas.

Note: Things that are NOT changing in the package:

• The name of the Github repository will not be changed. It will remain dbt_fivetran_log
• The package's project name will remain fivetran_log. You will not need to update your packages.yml reference.
• The default source schema will remain fivetran_log. The name of the source schema variable has changed though (fivetran_log_schema -> fivetran_platform_schema).

See details below!

PR #81 introduced the following changes (some unrelated to the connector name change):

🚨 Breaking Changes 🚨

• Updated the prefixes of each model from fivetran_log_* or stg_fivetran_log_* to fivetran_platform_* and stg_fivetran_platform_*, respectively.

• Updated the prefix of all package variables from fivetran_log_* to fivetran_platform_*.

• Updated the default build schema suffixes of package models from _stg_fivetran_log and _fivetran_log to _stg_fivetran_platform and _fivetran_platform respectively.

We recommend dropping the old schemas to eradicate the stale pre-name-change models from your destintation.

• Updated the name of the package's source from fivetran_log to fivetran_platform.
• Updated the name of the packages' schema files:
  • src_fivetran_log.yml -> src_fivetran_platform.yml
  • stg_fivetran_log.yml -> stg_fivetran_platform.yml
  • fivetran_log.yml -> fivetran_platform.yml
• Updated the freshness tests on the fivetran_platform source to be less stringent and more realistic. The following source tables have had their default fresness tests removed, as they will not necessarily update frequently:
  • connector
  • account
  • destination
  • destination_membership
  • user
• Updated the incremental strategy of the audit table model for BigQuery and Databricks users from merge to the more consistent insert_overwrite method. We have also updated the file_format to parquet and added a partition on a new sync_start_day field for Databricks. This field is merely a truncated version of sync_start.
  • Run a full refresh to capture these new changes. We recommend running a full refresh every so often regardless. See README for more details.
• The account_membership source table (and any of its transformations) has been deprecated. Fivetran deprecated this table from the connector in June 2023.

Considerations

• ⚠️ If you are overriding the fivetran_log source, you will need to update the overrides property to match the new source name (fivetran_platform).

Under the Hood

• Added documentation for fields missing yml entries.
• Incorporated the new fivetran_utils.drop_schemas_automation macro into the end of each Buildkite integration test job (PR #80).
• Updated the pull request templates (PR #80).

Full Changelog: v0.7.4...v1.0.0