I think we can get around this by adding a limit 0 to these all-null staging models in order to avoid fanout.
Relevant error log or model output
Database Error in model fivetran_platform__usage_mar_destination_history (models/fivetran_platform__usage_mar_destination_history.sql)
invalid input syntax for type date: "-01"
compiled Code at target/run/fivetran_log/models/fivetran_platform__usage_mar_destination_history.sql
Expected behavior
No error
dbt Project configurations
Quickstart
Package versions
Quickstart
What database are you using dbt with?
postgres
dbt Version
1.6.6
Additional Context
No response
Are you willing to open a PR to help address this issue?
[ ] Yes.
[ ] Yes, but I will need assistance and will schedule time during our office hours for guidance
Is there an existing issue for this?
Describe the issue
This line is failing with the below error message. I think this is occurring because we employ a
full outer join
in this CTE, on tables that are potentially 1-record all-NULL tables (https://github.com/fivetran/dbt_fivetran_log/blob/main/models/staging/stg_fivetran_platform__credits_used.sql and https://github.com/fivetran/dbt_fivetran_log/blob/main/models/staging/stg_fivetran_platform__usage_cost.sql)I think we can get around this by adding a
limit 0
to these all-null staging models in order to avoid fanout.Relevant error log or model output
Expected behavior
No error
dbt Project configurations
Quickstart
Package versions
Quickstart
What database are you using dbt with?
postgres
dbt Version
1.6.6
Additional Context
No response
Are you willing to open a PR to help address this issue?