jpedrick commented on issue #7172:
URL: https://github.com/apache/superset/issues/7172#issuecomment-850748020


   @mistercrunch I think from my perspective, I don't really care much about 
"Business Intelligence." I care about easy data presentation. I can't say for 
the Apache Superset community what Superset should become. Should it be, as you 
suggest, a subset of the data presentation space focused on the minimum 
standard of Business Intelligence, or should it be broadly more functional for 
scientific and statistical data presentation with BI simplifications?
   
   From the first paragraph of the documentation: "It is fast, lightweight, 
**intuitive**, and loaded with options that make it easy for users of **all 
skill sets** to **explore and visualize their data**". Many users here are 
saying forcing aggregation is not user-friendly, does not meet the needs of 
experienced data scientists and technical users, and makes exploring data 
difficult or impossible with SuperSet.
   
   Even for business intelligence applications, most BI experts will want the 
ability to see the raw data superimposed on their aggregated measures to notice 
outliers that might not match the filters they have predefined for alerting 
them to outliers. Forcing data to be hidden/aggregated adds a layer of 
indirection that can only lead to frustration and users avoiding SuperSet in 
favor of alternatives. 
   
   I would suggest SuperSet could easy support large dataset visualization 
similar to how matplotlib implements datashaders. On the backend, if the 
datapoints requested exceed the resolution of the plotting canvas, assume 
datashading is desired unless explicitly disabled.


-- 
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]

Reply via email to