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-refreshis 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_monthsvariable 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_statusfivetran_platform__schema_changelogfivetran_platform__audit_user_activityfivetran_platform__connection_daily_eventsfivetran_platform__audit_table(note: if you set or change this variable, rundbt run --full-refreshto ensure this incremental model reflects the updated window)
Under the Hood
- Tests out optimizations of
fivetran_platform__audit_tablefor smaller Postgres instances.- Creates two new macros:
convert_to_jsonandfivetran_log_json_parse_dev(a development version offivetran_log_json_parse) to consolidate JSON parsing and casting in Postgres and SQL Server. - Removes regex-based JSON check on the
LOG.message_datafield for Postgres. Postgres has a character limit of 10,485,760. Therefore,message_datais very likely not truncated or malformed. - Removes unnecessary
next_records_modifiedwindow function.
- Creates two new macros:
Full Changelog: v2.5.3-a1...v2.5.3-a2