dbt_fivetran_utils
dbt_fivetran_utils copied to clipboard
fivetran
Helper utils for our packages
**What change does this PR introduce?** Adds `fivetran_union_relations` macro. This was necessary for rolling union_data out to Zendesk, which has some source tables that have reserved-keywords for names (ie `timezone`)....
**What change does this PR introduce?** Adds SQLserver logic to the `wrap_in_quotes()` macro. this was necessary as the default logic (using backticks instead of double quotes) did not work with...
This macro is used only in `dbt_marketo`. Since this macro will soon be updated within in `dbt_marketo`, we should deprecate it here after it is moved.
# Feature Description A lot of effort has been made over the past year to include full coverage of testing for the fivetran_utils package to test against **all** Fivetran dbt...
We should review our macros and mark the outdated ones for deprecation. This will also require an audit of our packages to see which are using the old macros, or...
BQ introduced a native JSON data type (ala variants in snowflake maybe?) and some new JSON parsing functions. the ones we leverage in this package are now "legacy" in the...
Update the titular macro with this as the default. This is to allow for the case where we wish to append anything to any pass through fields. We ran into...
Currently, `fill_pass_through_columns` fails if the passthrough variable is not defined in the project yml. In order for us to eliminate the need to pre-define these variables in our packages, this...
Currently when a non-mapped passthrough/list-style variable is passed to `persist_pass_through_columns` macro, no error occurs but blank fields are generated. This macro should be updated to handle either list- or dict-...
Just tested this locally -- if we create a `models` folder to this package and add a docs.md file with definitions, all other packages that depend on this one will...