**DECISION:** Out-of-scope
------
After syncing offline with @john-bodley , it seems like we need to think more
about
### What kind of UI we have in mind on the explore page?
A. Users need to formulate query to get tabular data first, then map the
columns from intermediate table to the encoding channels (color, size, length,
position, etc.)
B. The controls list encoding channels, which users can put
columns/metrics/aggregates from datasource and our engine translates this back
into database query + post-query transformation.
### What operations should be done on back-end/front-end?
For example, group by and aggregates (count,sum,avg,etc.) should leverage
database.
Transforming table into tree nodes can be done in js.
What about multiple time series? The query engine needs to know that it is
dealing with time series so it will also group by time in the query.
`[{ name, time, value }]`
[ Full content available at:
https://github.com/apache/incubator-superset/issues/5692 ]
This message was relayed via gitbox.apache.org for [email protected]
