docs: document required_attributes and any_attributes on metrics - #1290
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EDxLPssdHreekX2y73SeRB
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Documentation validation✅ All blocking checks passed. Component system0 finding(s) across the corpus. Findings on lines this pull request touched are annotated inline in Files changed. |
This was referenced Sep 29, 2026
Metrics accept both keys. Column-level metrics inherit them from their dimension and can override each key; model-level metrics use their own. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01USjqEeuDVEJxmGdiVFfyZS
owlas
changed the title
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Relates: lightdash/lightdash#24709
Documents metric-level
required_attributes/any_attributes, added in lightdash/lightdash#30209. Merge after lightdash/lightdash#30209 ships.Behaviour:
metrics) use only their own keys; they inherit nothing from the columns they referencemetrics) inherit the dimension's keys; setting either key on the metric replaces the inherited value for that key only, which lets you expose an aggregate without exposing the columnChanges:
workspace-admin/user-attributes.mdx: new canonical section "Metric access control" (#metric-access-control), with dbt v1.10+, v1.9 and Lightdash YAML examples covering a model-level metric, an inheriting column metric and an overriding column metric. The summary list at the top now says the keys apply to tables, columns and metrics. The column-filtering notes mention the override.<Info>→<Note>.semantic-layer/metrics.mdx:required_attributes/any_attributesrows in the metric configuration table; the model-level note says to set the keys on the metric.embed/reference.mdx,embed/embed-metrics-catalog.mdx,agents/data-access.mdx: list metrics among the fieldsrequired_attributesapplies to, and describe inheritance and override.semantic-layer/dimensions.mdx: same wording; fixes the broken dbt examples (- name:/- salary:).validate:docspasses on the changed files. Not run:mint validate,mint broken-links(mint isn't available in the environment).🤖 Generated with Claude Code
https://claude.ai/code/session_01USjqEeuDVEJxmGdiVFfyZS