Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Joining druid datasources? #5209

Closed
1 of 3 tasks
MTShannon opened this issue Jun 15, 2018 · 2 comments
Closed
1 of 3 tasks

Joining druid datasources? #5209

MTShannon opened this issue Jun 15, 2018 · 2 comments
Labels
inactive Inactive for >= 30 days

Comments

@MTShannon
Copy link

Make sure these boxes are checked before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if any
  • I have reproduced the issue with at least the latest released version of superset
  • I have checked the issue tracker for the same issue and I haven't found one similar

Superset version

Expected results

Like the title states, is it possible to combine two druid datasources to use in a visualization? I've read that you can use views to join tables, but I couldn't find anything regarding Druid datasources.

Thanks

@ahsanshah
Copy link

I dont believe you can do "joins" per se in Druid. However, these may be potential options to consider:

  1. You can always use slices across Druid datasources on a dashboard and having a common Dimension Column name will allow filtering across those sources

  2. Superset recently has support for Multi-Line Chart which allows overlay of line charts which can indeed be across Druid data sources assuming a common Time Grain.

  3. Annotations across 2 charts. this is similar to Fix documentation #2 but down side is that you cannot filter across the annotation as far as I am aware.

If you really do need tight integration you would have to either do it in the ETL pre-Druid ingestion or perhaps customize the SQL Alchemy engine to meet your needs.

@stale
Copy link

stale bot commented Apr 10, 2019

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.

@stale stale bot added the inactive Inactive for >= 30 days label Apr 10, 2019
@stale stale bot closed this as completed Apr 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inactive Inactive for >= 30 days
Projects
None yet
Development

No branches or pull requests

2 participants