Skip to content

Package Updates (Breaking Changes!)

Compare
Choose a tag to compare
@fivetran-jamie fivetran-jamie released this 17 Mar 18:49
4774fc3

A bunch of breaking changes ahead!! 🚨🚨🚨

This new release:

  • Adds double underscores to model names (fivetran_log_connector_status is now fivetran_log__connector_status).
  • Renames the daily API calls model to fivetran_log__connector_daily_events, as it now includes daily metrics regarding record modifications and schema changes.
  • Assumes that Fivetran Log data is provided at the account level and removes functionality for unioning individual destination-level log connectors. This can now be configured in Fivetran's UI.
  • Creates a new fivetran_log__audit_table model that reports on the rows updated, deleted, and inserted/replaced into each table during connector syncs.
  • Creates a new fivetran_log__schema_changelog model that provides details surrounding each connector schema change event.
  • Deprecates the data_sync_status column from the final fivetran_log__connector_status model. Refer to the table's connector_health column.
  • Reverts the renaming of LOG.connector_id. The value of this column was previously erroneously reported as the connector name instead of the ID.
  • Incorporates model disablement variables to handle cases where the TRANSFORMATION and TRIGGER_TABLE tables do not exist.
  • Deprecates the destination_database column. Refer to destination_id and destination_name.
  • Incorporates custom schemas.