mistercrunch edited a comment on issue #7172: URL: https://github.com/apache/superset/issues/7172#issuecomment-850176654
Superset's explorer is used to explore multidimensional datasets, and semantically metrics in Superset are strictly defined aggregate expressions. That is the case for metric definitions in most BI tools. The dimensions / metric mental model is widely accepted and generally easy to reason about. Doing a sum of a single row is valid, personally fail to see why people see this as a problem. If you happen to add other columns/dimensions to your dataset, things will still work. There are complex implications here but if you'd like to say "I don't want Superset to not aggregate this" through the UI and happen to have duplicates in your dataset for whatever reason, or simply by check that box by mistake, there's a whole lot of implications, like dealing with high volume data and/or duplicates. In the current model, Superset has guaranties around the granularity of the queries it generates, if that's not the case, Superset has to trust that the user is right, or assert that the grain of the query is the one expected. Handling these exceptions and communicating them to the user "hey looks like you have dups an you should use an aggregate function" seem overall harder and less intuitive than the original proposition: "metrics are aggregate expressions". -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
