docs: clarify calendar cube join requirements #10272
Open
+10
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Both join dimensions must be of type time (timestamp) - The calendar cube's join dimension must be the primary_key
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the calendar cubes documentation to clarify two important requirements when joining a calendar cube to other cubes:
time(timestamp). The dimension on the calendar cube side and the dimension on the other cube side must both be timestamp dimensions.primary_key. The dimension used in the join condition on the calendar cube side must haveprimary_key: trueset.These requirements are critical for calendar cubes to function correctly and were not previously documented.