Incubator-superset: Related tables

[asheem]

Is your feature request related to a problem? Please describe.
Would it be possible to join tables so that selections made in one or more fields displays possible values in related tables?

Describe the solution you'd like
When fields are selected in related tables, resulting values are displayed in either tabular or chart format.

Describe alternatives you've considered
Available in other data visualization tools.

Additional context
Can be provided if required.

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label #enhancement to this issue, with a confidence of 0.86. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[mistercrunch]

The only way to do this at the moment is by using views as a datasource (where the view is making the join). We understand that there's performance impacts and in general we recommend denormalizing/materializing.

We may add support for joins in the future, where you could define many-to-one relationship to dimension tables (in the datasource editor) and define the join criteria there. Then the columns coming from these tables would show up under the "columns" tab. Presumably the SQL-generation logic would only join as needed.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

[asheem]

Thanks! The ability to view results based on selected values in multiple tables would be very helpful.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

[runningdata]

The only way to do this at the moment is by using views as a datasource (where the view is making the join). We understand that there's performance impacts and in general we recommend denormalizing/materializing.

We may add support for joins in the future, where you could define many-to-one relationship to dimension tables (in the datasource editor) and define the join criteria there. Then the columns coming from these tables would show up under the "columns" tab. Presumably the SQL-generation logic would only join as needed.

So what's the plan?