mistercrunch commented on issue #9887: URL: https://github.com/apache/incubator-superset/issues/9887#issuecomment-633827964
The data-centric approach (query + transform + map-data-to-viz-properties) as opposed to the visualization-property-centric approach is certainly interesting, but that last map phase is fairly challenging to design well so that it's intuitive to the user. This was discussed at length in the sessions leading to SIP-34. Some of the challenges with the query-centric approach are: - doing good guesswork around mapping data to viz properties attribute is challenging and we need to allow the user to override - forcing the right granularity: some visualization require different things (a particular number of dimensions, a particular number of metrics). While the "Query" panel seem like a conceptually universal thing, the mechanics / restrictions applied to it are tricky (say if we need to force you to pick exactly 2 dimensions and a single metric, or if you're not allowed to pick a dimensions [big number], or if you have to pick a metric and a secondary one is optional, ....). - for many users, if you're just trying to make a bar chart, or a big number, the whole query -> transform -> map mind gymnastic is a bit complicated. We should dig out the best design we had for this during the design biltz. The design would show a query panel with the viz-property-mapping within the dropped "pill" in the droppable area of the query (the wireframe would be worth 10k words here...). That seemed somewhat intuitive but I feel like that design/model couldn't support another layer of transformation that we disregarded at that time. One more thought, it's the fact that transformations are unevenly tricky, and we may want to categorize them: - **in-place mutations** - transforms that don't change the shape of the result set - are easy - **metric derivative** - a new computed metric work generally well with visualizations that support multiple metrics - **pivots** - where the shape of the data following the transformation is dynamic are generally tricky, the visualization has to expect a certain shape here. Clearly not any pivot table can be visualized by any type of visualization... - **grain changing**: many viz care a lot about having the perfect "grain" and some transforms could mess with that ---------------------------------------------------------------- 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]
