v2.0.0 dbt_fivetran_log
·
7 commits
to main
since this release
PR #144 includes the following updates:
Breaking Changes - Action Required
A
--full-refresh
is required after upgrading to prevent errors caused by naming and materialization changes. Additionally, downstream queries must be updated to reflect new model and column names.
-
The materialization of all
stg_*
staging models has been updated fromtable
toview
.- Previously
stg_*_tmp
models were views while the non-*_tmp
versions were tables. Now all are views to eliminate redundant data storage.
- Previously
-
Source Table Transition:
- The
CONNECTOR
source table is deprecated and replaced byCONNECTION
. During a brief transition period, both tables will be identical, butCONNECTOR
will stop receiving data and be removed at a later time.- This change clarifies the distinction: Connectors facilitate the creation of connections between sources and destinations.
- The
CONNECTION
table is now the default source.- For Quickstart users: The
CONNECTOR
will automatically be used ifCONNECTION
is not yet available. - For dbt Core users: Users without the
CONNECTION
source can continue usingCONNECTOR
by adding the following variable to your rootdbt_project.yml
file:vars: fivetran_platform_using_connection: false # default: true
- For more details, refer to the README.
- For Quickstart users: The
- The
-
New Columns:
- As part of the
CONNECTION
updates, the following columns have been added alongside theirconnector_*
equivalents:- INCREMENTAL_MAR:
connection_name
- LOG:
connection_id
- INCREMENTAL_MAR:
- As part of the
-
Renamed Models:
fivetran_platform__connector_status
→fivetran_platform__connection_status
fivetran_platform__connector_daily_events
→fivetran_platform__connection_daily_events
fivetran_platform__usage_mar_destination_history
→fivetran_platform__usage_history
stg_fivetran_platform__connector
→stg_fivetran_platform__connection
stg_fivetran_platform__connector_tmp
→stg_fivetran_platform__connection_tmp
NOTE: Ensure any downstream queries are updated to reflect the new model names.
- Renamed Columns:
- Renamed
connector_id
toconnection_id
andconnector_name
toconnection_name
in the following models:fivetran_platform__connection_status
- Also renamed
connector_health
toconnection_health
- Also renamed
fivetran_platform__mar_table_history
fivetran_platform__connection_daily_events
fivetran_platform__audit_table
fivetran_platform__audit_user_activity
fivetran_platform__schema_changelog
stg_fivetran_platform__connection
stg_fivetran_platform__log
connector_id
toconnection_id
only
stg_fivetran_platform__incremental_mar
connector_name
toconnection_name
only
- Renamed
NOTE: Ensure any downstream queries are updated to reflect the new column names.
Features
- Added macro
coalesce_cast
to ensure consistent data types when usingcoalesce
, preventing potential errors. - Added macro
get_connection_columns
for the newCONNECTION
source.
Documentation
- Updated documentation to reflect all renames and the source table transition.
Under the Hood (Maintainers Only)
- Updated consistency and integrity tests to align with naming changes.
- Refactored seeds and
get_*_columns
macros to reflect renames. - Added a new seed for the
CONNECTION
table. - Updated
run_models
to test new varfivetran_platform_using_connection
.
Full Changelog: v1.11.0...v2.0.0