clarify mf timespine confusion #6252
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
patkearns10
approved these changes
Oct 8, 2024
| - It needs to reference a column defined under the `columns` key, in this case, `date_hour` and `date_day`, respectively. | ||
| - The `standard_granularity_column` is the column that maps to one of our [standard granularities](/docs/build/dimensions?dimension=time_gran). This column must be set under the `columns` key and should have a grain that is finer or equal to any custom granularity columns defined in the same model. | ||
| - It needs to reference a column defined under the `columns` key, in this case, date_hour and date_day, respectively. | ||
| - It sets the granularity at the column-level using the `granularity` key, in this case, `hour` and `day`, respectively. | ||
| - MetricFlow will use the `standard_granularity_column` as the join key when joining the time spine table to other source table. | ||
|
|
||
| [The `custom_granularities` field](#custom-calendar), (available in Versionless and dbt v1.9 and higher) lets you specify non-standard time periods like `fiscal_year` or `retail_month` that your organization may use. |
There was a problem hiding this comment.
Should this be another bullet after custom_granularities?
|
thanks so much @patkearns10 ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 clarifies the confusing content explained by @patkearns10 in this internal slack thred