github fivetran/dbt_fivetran_log v2.5.3-a2
v2.5.3-a2 dbt_fivetran_log

pre-release5 hours ago

PR #184 is a pre-release that includes the following updates:

Schema Data Changes

3 total changes • 3 possible breaking changes

To prevent potential errors from naming and materialization updates, a --full-refresh is required after upgrading.

Data Models Change Type Old New Notes
stg_fivetran_platform__log_tmp Materializtion view table Intended to optimize downstream model runtime by reducing full table scans.

Feature Update

  • Adds the optional fivetran_platform_lookback_window_months variable to limit the number of records included in log-based models uniformly. When set to an integer (number of months), only log records within the specified window are included in downstream models. Unset by default. Full log history is included unless configured. See the README for configuration details. Affects the following models:
    • fivetran_platform__connection_status
    • fivetran_platform__schema_changelog
    • fivetran_platform__audit_user_activity
    • fivetran_platform__connection_daily_events
    • fivetran_platform__audit_table (note: if you set or change this variable, run dbt run --full-refresh to ensure this incremental model reflects the updated window)

Under the Hood

  • Tests out optimizations of fivetran_platform__audit_table for smaller Postgres instances.
    • Creates two new macros: convert_to_json and fivetran_log_json_parse_dev (a development version of fivetran_log_json_parse) to consolidate JSON parsing and casting in Postgres and SQL Server.
    • Removes regex-based JSON check on the LOG.message_data field for Postgres. Postgres has a character limit of 10,485,760. Therefore, message_data is very likely not truncated or malformed.
    • Removes unnecessary next_records_modified window function.

Full Changelog: v2.5.3-a1...v2.5.3-a2

Don't miss a new dbt_fivetran_log release

NewReleases is sending notifications on new releases.