PR #194 includes the following updates:
Schema/Data Change (--full-refresh required after upgrading)
9 total changes • 2 possible breaking changes
| Data Model(s) | Change type | Old | New | Notes |
|---|---|---|---|---|
| fivetran_platform__audit_table (Breaking) | Changed model | Tracks same-named tables in different schemas separately. Before, their write events could mix, so a record could show another schema's write times and row counts. Existing records for these tables may change. | ||
| stg_fivetran_platform__log (Breaking) | Materialization | view | table (only when fivetran_platform_log_start_date is set)
| Materializes as a table when the fivetran_platform_log_start_date variable is set, and filters to log records on or after that date. Downstream log-based models then exclude older records, so they can return fewer rows. The date filter applies after column transformations, reducing source scan costs for large log tables. Remains an unfiltered view when the variable is unset.
|
| fivetran_platform__sync_metrics | New model | Returns one record per completed sync with start/end times, status, reason, sync type, duration, volume, queries, rows extracted, and rows loaded, plus connection and destination details. total_loaded_rows counts insert, update, and delete operations, not distinct rows. Rows can include a mix of populated and null values because operations are tied to different events
| ||
| fivetran_platform__audit_trail_enriched | New model | Enriches each audit trail event with the names of the primary and secondary resources involved (a CONNECTION, DESTINATION, ACCOUNT, or USER) and the details of the user who performed the action. Only available for customers on the Enterprise plan and above. Requires the audit_trail source table, and is dynamically enabled in Quickstart while disabled by default otherwise. Self-managed dbt projects can enable by setting the fivetran_platform_using_audit_trail variable to true.
| ||
| fivetran_platform__transformation_run_log | New model | Surfaces transformation run events from the Fivetran log, including run timestamps, duration in HH:MM:SS format, per-step model success and failure counts, and overall run status. Requires the transformation_runs source table, is dynamically enabled in Quickstart while disabled by default otherwise. Self-managed dbt projects can enable by setting the fivetran_platform_using_transformations variable to true.
| ||
| fivetran_platform__connection_errors_and_warnings | New model | Unions error and warning events from the log (standard connections) and connector_sdk_log (Connector SDK connections) tables, enriched with connection_name.
| ||
| fivetran_platform__audit_table | New fields | rows_extractedrows_loaded
| Adds rows_extracted, the rows extracted from the source for the table during the sync, and rows_loaded, the insert, update, and delete operations on the table during the sync. rows_loaded counts operations, not distinct rows.
| |
| stg_fivetran_platform__audit_trail | New staging model | Records user actions performed within your Fivetran account (what was changed, by whom, and how). Only available for customers on the Enterprise plan and above, is dynamically enabled in Quickstart while disabled by default otherwise. Self-managed dbt projects can enable by setting the fivetran_platform_using_audit_trail variable to true.
| ||
| stg_fivetran_platform__connector_sdk_log | New staging model | Staging model for the new connector_sdk_log source table.
|
Feature Update
- Adds 4 new end models and 2 new staging models. See the Schema/Data Changes table above for details.
- Adds the
fivetran_platform_using_connector_sdk_logvariable (defaultfalse) to enable or disable theconnector_sdk_logsource and its downstream logic. Set this totrueto enable theconnector_sdk_logtable. See the README for details. - Adds the
fivetran_platform_using_audit_trailvariable (defaultfalse) to enable or disable theaudit_trailsource and its downstream logic. Set this totrueto enable theaudit_trailtable. Theaudit_trailtable is only available on the Enterprise plan and above. See the README for details. - Adds the optional
fivetran_platform_log_start_datevariable to control how much source log data is scanned/loaded. When set to a date (YYYY-MM-DD),stg_fivetran_platform__logfilters to log records on or after that date. As downstream incremental models grow, you can periodically move the start date forward to keep full-refresh scans manageable. See the README for details. Affectsfivetran_platform__connection_status,fivetran_platform__schema_changelog,fivetran_platform__audit_user_activity,fivetran_platform__connection_daily_events,fivetran_platform__audit_table,fivetran_platform__sync_metrics,fivetran_platform__connection_errors_and_warnings, andfivetran_platform__transformation_run_log(note: rundbt run --full-refreshafter setting or changing this variable).
Full Changelog: v2.5.3...v2.6.0