GitHub user fkostadinov edited a comment on the discussion: Add "metric" to show actual value of column, i.e. no aggregate
I just learned about this limitation today. This becomes an issue if you want to integrate Apache Superset with e.g. DBT semantic layer or Cube. The reason to use those tools is to guarantee (e.g. for regulatory reasons) the calculation of a specific value. Guarantee here is strict: You cannot simply change the SQL / aggregation code once defined without a governed sign-off process. That's what these tools allow you to do: governance (DBT) and security (Cube), in other words setting/definining required boundary conditions needed by regulators. This implies that I am forced to calculate those metrics in the underlying query layer, and I am not allowed to calculate the aggregations in Apache Superset directly. But that Apache Superset does not allow me to - except if I compromise and use e.g. a "SUM" or "AVG" function on values, which is not exactly the most preferred approach in a regulated environment. Unfortunately, that's a no-go criterion for me, for the reasons provided. I guess, there's really not a lot to be done here, given this violates the original architecture of Apache Superset. Which is indeed a bummer. :( GitHub link: https://github.com/apache/superset/discussions/19182#discussioncomment-15479951 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
