You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that this logic is not working as expected. We've seen in some Snowflake warehouses that the below error message is being served and causing a data model failure. As such, there must be something that needs to be adjusted within the logic to ensure we can account for leap years.
Relevant error log or model output
Date '2025-2-29' is not recognized
Expected behavior
The data model can handle leap years
Possible solution
Update this logic to account for the leap year. We may need to play around with the date format in Snowflake and make sure we can update the logic to work as expected.
Edit: I have since creating this issue that the error is also occurring potentially on BigQuery warehouses. We should probably bring this entire logic into scope for all warehouses when addressing the issue.
dbt Project configurations
Default
Package versions
Latest
What database are you using dbt with?
snowflake and bigquery
How are you running this dbt package?
Fivetran Quickstart Data Model
dbt Version
Latest
Additional Context
No response
Are you willing to open a PR to help address this issue?
Yes.
Yes, but I will need assistance.
No.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Describe the issue
It seems that this logic is not working as expected. We've seen in some Snowflake warehouses that the below error message is being served and causing a data model failure. As such, there must be something that needs to be adjusted within the logic to ensure we can account for leap years.
Relevant error log or model output
Date '2025-2-29' is not recognized
Expected behavior
The data model can handle leap years
Possible solution
Update this logic to account for the leap year. We may need to play around with the date format in Snowflake and make sure we can update the logic to work as expected.
Edit: I have since creating this issue that the error is also occurring potentially on BigQuery warehouses. We should probably bring this entire logic into scope for all warehouses when addressing the issue.
dbt Project configurations
Default
Package versions
Latest
What database are you using dbt with?
snowflake and bigquery
How are you running this dbt package?
Fivetran Quickstart Data Model
dbt Version
Latest
Additional Context
No response
Are you willing to open a PR to help address this issue?
The text was updated successfully, but these errors were encountered: