-
Notifications
You must be signed in to change notification settings - Fork 114
Open
Labels
enhancementNew feature or requestNew feature or requesttriageTasks that need to be triagedTasks that need to be triaged
Description
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 metricflow functionality, rather than a Big Idea better suited to a discussion
Describe the feature
Let's say I have:
- semantic model order_items --> linked to this there's a metric called "arr"
- semantic model product_lvl_1 --> highest categorization of products
- semantic model product_lvl_2
- semantic model product_lvl_3
- semantic model product_lvl_4
- semantic model product_lvl_5 --> single SKUs
Every semantic model product_lvl_N refers, as foreign entity, the product_lvl_(N-1).
The semantic model order_items refers, as foreign entity, the product_lvl_5 semantic model.
Expectations: ideally, we should be able to run all below queries:
- dbt sl query --metrics arr --group-by product_lvl_5__name --> OK
- dbt sl query --metrics arr --group-by product_lvl_4__name --> OK
- dbt sl query --metrics arr --group-by product_lvl_3__name --> OK
- dbt sl query --metrics arr --group-by product_lvl_2__name --> KO
- dbt sl query --metrics arr --group-by product_lvl_1__name --> KO
Issue: the queries tagged as KO fail because the dimensions product_lvl_2__name and product_lvl_1__name are not recognized as dimensions to slice the arr metric with. This is confirmed by the output of dbt sl list dimensions --metrics arr.
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
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requesttriageTasks that need to be triagedTasks that need to be triaged