PR #144 includes the following updates:
Breaking Changes - Action Required
A
--full-refreshis 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 fromtabletoview.- Previously
stg_*_tmpmodels were views while the non-*_tmpversions were tables. Now all are views to eliminate redundant data storage.
- Previously
-
Source Table Transition:
- The
CONNECTORsource table is deprecated and replaced byCONNECTION. During a brief transition period, both tables will be identical, butCONNECTORwill 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
CONNECTIONtable is now the default source.- For Quickstart users: The
CONNECTORwill automatically be used ifCONNECTIONis not yet available. - For dbt Core users: Users without the
CONNECTIONsource can continue usingCONNECTORby adding the following variable to your rootdbt_project.ymlfile: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
CONNECTIONupdates, 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_statusfivetran_platform__connector_daily_events→fivetran_platform__connection_daily_eventsfivetran_platform__usage_mar_destination_history→fivetran_platform__usage_historystg_fivetran_platform__connector→stg_fivetran_platform__connectionstg_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_idtoconnection_idandconnector_nametoconnection_namein the following models:fivetran_platform__connection_status- Also renamed
connector_healthtoconnection_health
- Also renamed
fivetran_platform__mar_table_historyfivetran_platform__connection_daily_eventsfivetran_platform__audit_tablefivetran_platform__audit_user_activityfivetran_platform__schema_changelogstg_fivetran_platform__connectionstg_fivetran_platform__logconnector_idtoconnection_idonly
stg_fivetran_platform__incremental_marconnector_nametoconnection_nameonly
- Renamed
NOTE: Ensure any downstream queries are updated to reflect the new column names.
Features
- Added macro
coalesce_castto ensure consistent data types when usingcoalesce, preventing potential errors. - Added macro
get_connection_columnsfor the newCONNECTIONsource.
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_*_columnsmacros to reflect renames. - Added a new seed for the
CONNECTIONtable. - Updated
run_modelsto test new varfivetran_platform_using_connection.
Full Changelog: v1.11.0...v2.0.0