You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 metricflow functionality, rather than a Big Idea better suited to a discussion
Describe the feature
Currently, running mf list dimensions looks something like this:
$ mf list dimensions --metrics jumbo_orders
✔ 🌱 We've found 12 common dimensions for metrics ['jumbo_orders'].
• location_name
• ds
• is_food_order
• is_drink_order
• order_total_dim
• is_large_order
• customer_name
• count_lifetime_orders
• lifetime_spend
• customer_type
• first_ordered_at
• last_ordered_at
The thing is, ds is the underlying dimension name for the aggregation time dimension for jumbo_orders, which can also be accessed via the metric_time alias, but unless the calling user has read our documentation and remembers that metric_time is the name to use, they might not realize that the best way to query this metric - particularly if the query includes other metrics with different aggregation time dimensions - is to use the metric_time alias.
Ideally we'd include metric_time in this output list somewhere. For now, it's probably sufficient to simply hard-code the dimension name in the list, but ideally this would be something we could resolve.
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
The text was updated successfully, but these errors were encountered:
Is this your first time submitting a feature request?
Describe the feature
Currently, running
mf list dimensions
looks something like this:The thing is,
ds
is the underlying dimension name for the aggregation time dimension for jumbo_orders, which can also be accessed via themetric_time
alias, but unless the calling user has read our documentation and remembers thatmetric_time
is the name to use, they might not realize that the best way to query this metric - particularly if the query includes other metrics with different aggregation time dimensions - is to use themetric_time
alias.Ideally we'd include metric_time in this output list somewhere. For now, it's probably sufficient to simply hard-code the dimension name in the list, but ideally this would be something we could resolve.
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
The text was updated successfully, but these errors were encountered: