Upgrade project to dbt 1.9

* set dbt version minimum to 1.9.0
* use new time spine config

Author: ataft

dbt_project.yml

@@ -2,9 +2,9 @@
 # and underscores. A good package name should reflect your organization's
 # name or the intended use of these models
 name: "dbt_business_intelligence"
-version: "1.7.0"
+version: "1.9.0"
 config-version: 2
-require-dbt-version: ">=1.7.0"
+require-dbt-version: ">=1.9.0"
 # This setting configures which "profile" dbt uses for this project.
 profile: "dbt_business_intelligence"
 # These configurations specify where dbt should look for different types of files.

models/schema.yml

@@ -298,6 +298,8 @@ models:
 
   - name: dim_date
     description: The Order Date dimension allows you to analyze metrics across time periods at many levels of granularity (year, quarter, month, day).
+    time_spine:
+      standard_granularity_column: date_day
     config:
       contract:
         enforced: false
@@ -315,6 +317,7 @@ models:
           - type: primary_key
             warn_unenforced: false
       - name: date_day
+        granularity: day
         data_type: date
         meta:
           label: Order Date

models/staging/metricflow_time_spine.sql

@@ -11,4 +11,4 @@
 {%- set start_date = dates['data'][0][0] -%}
 {%- set end_date = dates['data'][0][1] -%}
 
-{{ dbt_date.get_date_dimension(start_date, end_date) }}
+{{ dbt_date.get_date_dimension(start_date, end_date) }}