Skip to content

docs: clarify calendar cube join requirements #10272

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
AvilaJulio wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs: clarify calendar cube join requirements #10272

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/pages/product/data-modeling/concepts/calendar-cubes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<CodeTabs>

```yaml
Expand Down