Skip to content
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.

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

[idea] Add MF time spine behavior change #6387

Closed
1 of 4 tasks
DevonFulcher opened this issue Oct 30, 2024 · 1 comment · Fixed by #6408
Closed
1 of 4 tasks

[idea] Add MF time spine behavior change #6387

DevonFulcher opened this issue Oct 30, 2024 · 1 comment · Fixed by #6408
Assignees
Labels
content Improvements or additions to content idea Proposes an idea for new content

Comments

@DevonFulcher
Copy link
Contributor

Which of these best describes you?

  • dbt Community member
  • Partner
  • dbt Labs employee
  • Other

What's your idea for new content?

To this page https://docs.getdbt.com/reference/global-configs/behavior-changes, a new behavior change should be added. The exact name is TBD. This behavior change is to indicate how the MF time spine should now be configured according to this documentation https://docs.getdbt.com/docs/build/metricflow-time-spine#custom-calendar- (see the change in version v1.8 and v1.9 of that page). Specifically, the timespine should be configured in yaml, not with the metricflow_time_spine.sql model. The implementation of this behavior change is in this PR dbt-labs/dbt-core#10857.

Where would you recommend this content live on the docs.getdbt.com?

https://docs.getdbt.com/reference/global-configs/behavior-changes

@DevonFulcher DevonFulcher added content Improvements or additions to content idea Proposes an idea for new content labels Oct 30, 2024
@DevonFulcher
Copy link
Contributor Author

The name of the behavior change is require_yaml_configuration_for_mf_time_spines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content idea Proposes an idea for new content
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants