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
There are cases where a count distinct is too computationally heavy, resulting in slow queries and high costs. Approximate counts can be much faster while still being accurate. Example measure:
Plain count distincts aren't an option due to performance. When using semantic models built on top of pre aggregated models, we will lose too much flexibility.
Who will this benefit?
No response
Are you interested in contributing this feature?
Yes
Anything else?
Approx percentiles already exists in metricflow: #395
Similar measure in Looker:
measure: apx_unique_count {type: count_distinctapproximate: yes # default value is nosql: ${id} ;;}
The text was updated successfully, but these errors were encountered:
Is this your first time submitting a feature request?
Describe the feature
There are cases where a count distinct is too computationally heavy, resulting in slow queries and high costs. Approximate counts can be much faster while still being accurate. Example measure:
Describe alternatives you've considered
Plain count distincts aren't an option due to performance. When using semantic models built on top of pre aggregated models, we will lose too much flexibility.
Who will this benefit?
No response
Are you interested in contributing this feature?
Yes
Anything else?
Approx percentiles already exists in metricflow:
#395
Similar measure in Looker:
The text was updated successfully, but these errors were encountered: