Closed fivetran-jamie closed 2 years ago
Hi,
Sharing our dbt_project.yml
configs for that specific package:
vars:
microsoft_ads_schema: bingads
microsoft_ads_database: fivetran-data-culture-big-vv9p
microsoft_ads_source:
microsoft_auto_tagging_enabled: true
models:
microsoft_ads_source:
+schema: staging
+materialized: view
microsoft_ads:
+schema: marketing # leave blank for just the target_schema
thanks @MaximeLagresle ! so i think i may have found the culprit here. could you try out my working branch and see if the uniqueness test is still failing?
# packages.yml
packages:
- git: https://github.com/fivetran/dbt_microsoft_ads_source.git
revision: bug/ad-history-uniqueness
Hey Jamie,
Thanks so much for quickly looking into that!
Unfortunately, I still have the error…
Here’s what I did:
dbt deps
dbt test
Let me know if I should do anything else!
ah i think you need to dbt run
in between the dbt deps
and dbt test
-- could you try that?
@fivetran-jamie my bad, you're right it works now!
great! this is merged and released
great! thanks @fivetran-jamie !
Are you a current Fivetran customer?
fivetran made issue (but this from veronica beard)
Describe the bug
Uniqueness test is failing on the staging ad_history table. in the customer's raw table
ad_history
table, adid
||modified_time
are indeed unique, so I am thinking that the joins withad_group
and/orcampaign
are causing fanoutSteps to reproduce
Expected behavior
the test should pass!
Project variables configuration
Package Version
Warehouse
- [x] BigQuery - [ ] Redshift - [ ] Snowflake - [ ] Postgres - [ ] Databricks - [ ] Other (provide details below) **Additional context** **Screenshots**Please indicate the level of urgency
Are you interested in contributing to this package?