-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add Slice support for arbitrary queries (including parameterization) #1203
Comments
Very interesting idea, how will that work with 'group by', 'metrics' parameters in various viz types? |
The "query parameters" would be completely independent of the typical "group by" and "metrics" fields. |
Since almost every type of visualization requires 'groupby' and 'metrics' Jparks2532 notifications@github.com于2016年9月28日周三 上午10:28写道:
|
Please don't get too hung up on the example that I provided. It's mainly there to show how you can pass in parameters into an arbitrary query. |
is this feature implemented in Superset? |
Yes pretty much, by following the "Visualize" button in SQL lab you're essentially running the explore view against your SQL statement as a subquery, and this SQL statement can be templated and receive url parameters. |
* fix(plugin-chart-echarts): add gauge cross filtering * fix(plugin-chart-echarts): fix lint * fix(plugin-chart-echarts): use constants
* fix(plugin-chart-echarts): add gauge cross filtering * fix(plugin-chart-echarts): fix lint * fix(plugin-chart-echarts): use constants
* fix(plugin-chart-echarts): add gauge cross filtering * fix(plugin-chart-echarts): fix lint * fix(plugin-chart-echarts): use constants
* fix(plugin-chart-echarts): add gauge cross filtering * fix(plugin-chart-echarts): fix lint * fix(plugin-chart-echarts): use constants
Slice support for arbitrary queries (including parameterization) would enable all types of use cases where a materialized table or view doesn't quite work. For instance, the following query template could serve as the source for a Slice:
query:
Users could pass in parameters at query time.
The text was updated successfully, but these errors were encountered: