PR #31 includes the following breaking changes:
- Dispatch update for dbt-utils to dbt-core cross-db macros migration. Specifically
{{ dbt_utils.<macro> }}
have been updated to{{ dbt.<macro> }}
for the below macros:any_value
bool_or
cast_bool_to_text
concat
date_trunc
dateadd
datediff
escape_single_quotes
except
hash
intersect
last_day
length
listagg
position
replace
right
safe_cast
split_part
string_literal
type_bigint
type_float
type_int
type_numeric
type_string
type_timestamp
array_append
array_concat
array_construct
- For
current_timestamp
andcurrent_timestamp_in_utc
macros, the dispatch AND the macro names have been updated to the below, respectively:dbt.current_timestamp_backcompat
dbt.current_timestamp_in_utc_backcompat
packages.yml
has been updated to reflect new defaultfivetran/fivetran_utils
version, previously[">=0.3.0", "<0.4.0"]
now[">=0.4.0", "<0.5.0"]
.packages.yml
has been updated to reflect the most up to date version of dbt-expectations[">=0.8.0", "<0.9.0"]
.- The
regexp_instr
macro has been added to the macros folder as a shim for spark adapters. Additional details for how to disaptch the macro have been added to the README Databricks compatibility section.
- Added
'databricks'
insrc_google_ads.yml
for database configs in order to be compatible for an earlier release of the dbt-databricks adapter. #32 - Updated
README.md
to reflectdbt-labs/spark_utils
in dependency matrix. #32
- The
adwords
api version of the package has been fully removed. As the Fivetran Google Ads connector now requires the Google Ads API, this functionality is no longer used. (#29) - The declaration of passthrough variables within your root
dbt_project.yml
has changed. To allow for more flexibility and better tracking of passthrough columns, you will now want to define passthrough metrics in the following format: (#29)
This applies to all passthrough metrics within the
dbt_google_ads_source
package and not just thegoogle_ads__ad_stats_passthrough_metrics
example.
vars:
google_ads__ad_stats_passthrough_metrics:
- name: "my_field_to_include" # Required: Name of the field within the source.
alias: "field_alias" # Optional: If you wish to alias the field within the staging model.
PR #29 includes the following changes:
-
Addition of the following staging models which pull from the source counterparts. The inclusion of the additional
_stats
source tables is to generate a more accurate representation of the Google Ads data. For example, not all Ad types are included within thead_stats
table. Therefore, the addition of the further grain reports will allow for more flexibility and accurate Google Ad reporting.stg_google_ads__account_stats
stg_google_ads__ad_group_criterion_history
stg_google_ads__ad_group_stats
stg_google_ads__campaign_stats
stg_google_ads__keyword_stats
-
Inclusion of additional passthrough metrics:
google_ads__ad_group_stats_passthrough_metrics
google_ads__campaign_stats_passthrough_metrics
google_ads__keyword_stats_passthrough_metrics
google_ads__account_stats_passthrough_metrics
-
README updates for easier navigation and use of the package.
-
Addition of identifier variables for each of the source tables to allow for further flexibility in source table direction within the dbt project.
-
Included grain uniqueness tests for each staging table.
- The
api_source
variable is now defaulted togoogle_ads
as opposed toadwords
. The Adwords API has since been deprecated by Google and is now no longer the standard API for the Google Ads connector. Please ensure you are using a Google Ads API version of the Fivetran connector before upgrading this package. (#28)- Please note, the
adwords
version of this package will be fully removed from the package in August of 2022. This means, models undermodels/adwords_connector
will be removed in favor ofmodels/google_ads_connector
models.
- Please note, the
- The
account
source table has been renamed to beaccount_history
. This has been reflected in this release. (#25) - The
ad_final_url_history
model has been removed from the connector. The url fields are now references within thefinal_urls
field within thead_history
table. (#25)- Please be aware that the logic in the
stg_google_ads__ad_history
model for the Google Ads API will only pull through the first url in thefinal_urls
list. This column should contain only one url. However, in the even that two are include a test will warn you that the other urls have been removed from the final model.
- Please be aware that the logic in the
🎉 dbt v1.0.0 Compatibility 🎉
- Adjusts the
require-dbt-version
to now be within the range [">=1.0.0", "<2.0.0"]. Additionally, the package has been updated for dbt v1.0.0 compatibility. If you are using a dbt version <1.0.0, you will need to upgrade in order to leverage the latest version of the package.- For help upgrading your package, I recommend reviewing this GitHub repo's Release Notes on what changes have been implemented since your last upgrade.
- For help upgrading your dbt project to dbt v1.0.0, I recommend reviewing dbt-labs upgrading to 1.0.0 docs for more details on what changes must be made.
- Upgrades the package dependency to refer to the latest
dbt_fivetran_utils
. The latestdbt_fivetran_utils
package also has a dependency ondbt_utils
[">=0.8.0", "<0.9.0"].- Please note, if you are installing a version of
dbt_utils
in yourpackages.yml
that is not in the range above then you will encounter a package dependency error.
- Please note, if you are installing a version of
- Renaming of the folder names within the
dbt_project.yml
to match the current spelling of the/models/
folder names. This allows for the materialization of thetmp
models to accurately be materialized as views. (#19)
Refer to the relevant release notes on the Github repository for specific details for the previous releases. Thank you!