-
Notifications
You must be signed in to change notification settings - Fork 215
Open
Labels
cloudIssues related to dbt CloudIssues related to dbt Cloudfeature:incrementalIssues related to incremental materializationsIssues related to incremental materializationsfeature:partitioningIssues related to table partitioningIssues related to table partitioningfeature:showIssues related to dbt show commandIssues related to dbt show commandpkg:dbt-bigqueryIssue affects dbt-bigqueryIssue affects dbt-bigquerytype:bugSomething isn't working as documentedSomething isn't working as documented
Description
Is this a new bug in dbt-bigquery?
- I believe this is a new bug in dbt-bigquery
- I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
See this internal Slack thread for details:
https://dbt-labs.slack.com/archives/C05FWBP9X1U/p1692582407653009
Expected Behavior
See internal Slack thread for details.
Steps To Reproduce
See above (and below).
{{
config(
materialized="incremental",
incremental_strategy="insert_overwrite",
partition_by={
"field": "created_at_date",
"data type: "DATE",
"granularity": "day",
})
}}
select * from {{ ref("incremental source date") }}
where created_at_date >= _dbt_max_partitionRelevant log output
No response
Environment
- OS:
- Python:
- dbt-core:
- dbt-bigquery:Additional Context
No response
tanghyd and ricardolohmannstelios-c
Metadata
Metadata
Assignees
Labels
cloudIssues related to dbt CloudIssues related to dbt Cloudfeature:incrementalIssues related to incremental materializationsIssues related to incremental materializationsfeature:partitioningIssues related to table partitioningIssues related to table partitioningfeature:showIssues related to dbt show commandIssues related to dbt show commandpkg:dbt-bigqueryIssue affects dbt-bigqueryIssue affects dbt-bigquerytype:bugSomething isn't working as documentedSomething isn't working as documented
