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
Snippet
01:09:20 Completed with 1 error and 0 warnings:
01:09:20
01:09:20 Compilation Error in model dim_date (dbt_demo/models/XXX/datamarts/customer_service/dim_date.sql)
int() argument must be a string, a bytes-like object or a real number, not 'NoneType'>in macro default__get_intervals_between (macros/sql/date_spine.sql)
> called by macro get_intervals_between (macros/sql/date_spine.sql)
> called by macro default__date_spine (macros/sql/date_spine.sql)
> called by macro date_spine (macros/sql/date_spine.sql)
> called by model dim_date (dbt_demo/models/adventureworks/datamarts/customer_service/dim_date.sql)
Last seen working on Jan 24th. Then another issue came up that I only just resolved, per issue (and hence why I fixed version of databricks-sdk). I haven't tested this functionality until yesterday, which is when I first noticed it was broken.
The text was updated successfully, but these errors were encountered:
hazvk
changed the title
[Bug] <title>
[Bug] dbt_utils.date_spine is not working as expected
Mar 8, 2024
hazvk
changed the title
[Bug] dbt_utils.date_spine is not working as expected
[Bug] dbt_utils.date_spine gives error when using legitimately
Mar 8, 2024
hazvk
changed the title
[Bug] dbt_utils.date_spine gives error when using legitimately
[Bug] dbt_utils.date_spine gives Python error
Mar 8, 2024
Is this a new bug in dbt-core?
Current Behavior
Running this model and using
dbt_utils.date_spine
used to work. I now get an error I can't get to the bottom of.Expected Behavior
Should evaluate and give a table
Steps To Reproduce
With dbt on local machine:
dbt build -f
Relevant log output
Environment
Which database adapter are you using with dbt?
other (mention it in "Additional Context")
Additional Context
Using dbt-databricks==1.6.8
Last seen working on Jan 24th. Then another issue came up that I only just resolved, per issue (and hence why I fixed version of
databricks-sdk
). I haven't tested this functionality until yesterday, which is when I first noticed it was broken.The text was updated successfully, but these errors were encountered: