Support time_granularity and date_part parameters in Dimension object

This is supported in JDBC already, so this will create a more consistent experience for customers.
dbt-labs · Sep 12, 2024 · 5bb6014 · 5bb6014
1 parent 47f831e
commit 5bb6014
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/dbt_semantic_interfaces/call_parameter_sets.py b/dbt_semantic_interfaces/call_parameter_sets.py
@@ -20,7 +20,8 @@ class DimensionCallParameterSet:
 
     entity_path: Tuple[EntityReference, ...]
     dimension_reference: DimensionReference
-    # TODO: MFS Jinja allows grain and date part in Dimension(...). Should we allow them here, too, for consistency?
+    time_granularity: Optional[TimeGranularity] = None
+    date_part: Optional[DatePart] = None
 
 
 @dataclass(frozen=True)

diff --git a/pyproject.toml b/pyproject.toml
@@ -1,6 +1,6 @@
 [project]
 name = "dbt-semantic-interfaces"
-version = "0.7.1"
+version = "0.7.2"
 description = 'The shared semantic layer definitions that dbt-core and MetricFlow use'
 readme = "README.md"
 requires-python = ">=3.8"