PR #140 includes the following updates:
Breaking Changes
A
--full-refresh
is recommended after upgrading to ensure historical records in incremental models are refreshed.
- Updated the
fivetran_log_json_parse
macro for Redshift to returnNULL
instead of an empty string when a JSON path is not found. This resolves errors caused by casting empty strings to integers in Redshift. - Standardized the
message_data
field from theLOG
source, in which JSON key names can appear in both camelCase (e.g.,{"totalQueries":5}
) and snake_case (e.g.,{"total_queries":5}
) formats, depending on the Fivetran connector version. Thefivetran_platform__audit_table
andfivetran_platform__connector_daily_events
models now convert all key names to snake_case for consistency. - These changes are considered breaking because the standardization of key names (e.g.,
totalQueries
tototal_queries
) may impact downstream reporting by including previously ignored values.
Under the Hood (Maintainers Only)
- Enhanced seed data for integration testing to include the different spellings and ensure compatibility with Redshift.
Full Changelog: v1.9.1...v1.10.0