[Drilldown]Support mapping of source/target columns in Cross-Filters

[cccs-jc]

This is mock-up of a dashboard with two Charts. The first chart is a table of flights between a originating airport and a destination airport. Columns include ORIGINATING_AIRPORT, DESTINATION_AIRPORT

The second chart gives details about a given airport. Columns include AIRPORT, LOCATION, BUILT

The idea would be to use cross-filtering in order to display the details of the airport selected in the flights table.

Notice that the datasets used in the charts do not share a common airport column name. Currently cross-filter require matching source/target column names.

You can also imagine a Slack dataset where columns might be "USER_MENTION", "USER_REACTION", "USER_COMMENT" and a user details table keyed on "USER_ID".

In the cross-filtering mechanism it would be great to have a means to map a given source column to a target filter column.

[junlincc]

hey jc, the feature you are proposing is called 'drilldown', similar to cross-filtering. instead of changing a 'where clause', drill down is basically changing the dimension. enabling it is now our top priority and would love to use some help from you.
lmk your plan on contributing 🙏 @cccs-jc

[cccs-jc]

Proposing to augment the Explore CUSTOMIZE COLUMNS. Adding a means to specify the emitted filter name.

@villebro's comment:
That’s a good approach. To avoid cluttering the UI, we need to start working on dynamic controls to be able to do “progressive disclosure” of fields. In this case, the emitted filter option would be shown only if “Emit filters” is enabled

[jhult]

@junlincc and @cccs-jc, did apache-superset/superset-ui#1157 ever make its way into Superset? I don't see anything on a table chart (even with "Emit Dashboard Cross Filters" enabled).

It would also be nice to have this for other (all?) chart types (such as a pie chart).

[stale]

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.

[jhult]

@junlincc and @cccs-jc, any thoughts on my previous comment?

[rusackas]

Spoke with @cccs-tom and @geido about this on Superset Slack, and it sounds like it's still valid.

[rusackas]

I'm tempted to close this since it's more of a proposal than a bug report, and I'm not sure anyone's planning to work on the effort. I'd propose closing this and revisiting the effort with a new Issue/PR when relevant. Any objections?

[cccs-rc]

No objections from us. :)