From 16c6fbabf44f20c2069e6beb294f531e0ed7aaf5 Mon Sep 17 00:00:00 2001 From: AvilaJulio Date: Fri, 19 Dec 2025 09:01:43 -0600 Subject: [PATCH] docs: clarify calendar cube join requirements - Both join dimensions must be of type time (timestamp) - The calendar cube's join dimension must be the primary_key --- .../product/data-modeling/concepts/calendar-cubes.mdx | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/pages/product/data-modeling/concepts/calendar-cubes.mdx b/docs/pages/product/data-modeling/concepts/calendar-cubes.mdx index 55fcf42a3b2b3..7e87e0f1edd45 100644 --- a/docs/pages/product/data-modeling/concepts/calendar-cubes.mdx +++ b/docs/pages/product/data-modeling/concepts/calendar-cubes.mdx @@ -21,6 +21,16 @@ Calendar cubes are [cubes][ref-cubes] where the [`calendar` parameter][ref-cubes is set to `true`. This indicates that the cube is a calendar cube and allow the use of custom time shifts and granularities. +### Requirements + +When joining a calendar cube to other cubes, the following requirements must be met: + +- **Both join dimensions must be of type `time` (timestamp).** The dimension on the + calendar cube side and the dimension on the other cube side must both be timestamp + dimensions. +- **The calendar cube's join dimension must be the `primary_key`.** The dimension used + in the join condition on the calendar cube side must have `primary_key: true` set. + ```yaml