rumbin commented on issue #7172: URL: https://github.com/apache/superset/issues/7172#issuecomment-850193699
I think that we need to see that there are two worlds. One ist the one of BI tools where it is very common to only show aggregated values. Then there is the world of technical users who are used to plotting the unaggregated values with tools like Excel, Origin, MATLAB, Python. The thing is, that these worlds happen to converge at some companies. Technical data (shopfloor, production machines) gets stored in Data Warehouses together with correlated business data. And people desire to explore both with one single tool. Technically oriented users, like e.g. product developers or quality engineers, might start their investigations on aggregated data but soon need to dig down to the unaggregated values in order to see things clearer. Very often these people need to plot 2-D scatter plots of two raw dimensions for determining the correlation of these dimensions. As a real world example, take, e.g. pressure-temperature diagrams, hysteresis plots, current-voltage, .... In a technical world these are ubiquitous. I agree on your concerns regarding the potentially huge amount or returned data, @mistercrunch. However, I think that the LIMITs that Superset applies anyway will minimize the damage here. We just need to ensure that the user is well aware of the applied limit. In well-built dashboards the user would need to narrow down the amount of data by means of filters until displaying the unaggregated data is really useful. This can to a certain amount be accomplished by employing Jinja logic, I suppose. -- 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]
