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

[Feature] Add default_granularity to metric spec #10376

Open
3 tasks done
courtneyholcomb opened this issue Jun 27, 2024 · 0 comments · May be fixed by #10378
Open
3 tasks done

[Feature] Add default_granularity to metric spec #10376

courtneyholcomb opened this issue Jun 27, 2024 · 0 comments · May be fixed by #10378
Assignees
Labels
artifact_minor_upgrade To bypass the CI check by confirming that the change is not breaking enhancement New feature or request semantic Issues related to the semantic layer triage

Comments

@courtneyholcomb
Copy link
Contributor

Is this your first time submitting a feature request?

  • I have read the expectations for open source contributors
  • I have searched the existing issues, and I could not find an existing issue for this feature
  • I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature

Add default_granularity to metric spec.
Currently, metric_time defaults to the smallest available granularity. Now that we're enabling sub-daily granularities, users will likely be surprised to see metric_time default to second or anything smaller than day. To enable users to continue defaulting to a more useful granularity while still enabling smaller granularities for a given time dimension, we will allow them to specify their default_granularity in the metric spec. This will default to day, ensuring that this is not a breaking change and the behavior of metric_time does not change until the user specifies a different granularity here.

Describe alternatives you've considered

No response

Who will this benefit?

No response

Are you interested in contributing this feature?

No response

Anything else?

No response

@courtneyholcomb courtneyholcomb added enhancement New feature or request triage semantic Issues related to the semantic layer artifact_minor_upgrade To bypass the CI check by confirming that the change is not breaking labels Jun 27, 2024
@courtneyholcomb courtneyholcomb self-assigned this Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
artifact_minor_upgrade To bypass the CI check by confirming that the change is not breaking enhancement New feature or request semantic Issues related to the semantic layer triage
Projects
None yet
1 participant