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

New feature consideration: use python datashader package #4492

Closed
3 tasks done
ariejdl opened this issue Feb 27, 2018 · 3 comments
Closed
3 tasks done

New feature consideration: use python datashader package #4492

ariejdl opened this issue Feb 27, 2018 · 3 comments
Labels
inactive Inactive for >= 30 days

Comments

@ariejdl
Copy link

ariejdl commented Feb 27, 2018

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

  • 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
  • I have checked the superset logs for python stacktraces and included it here as text if any

Superset version

0.23

Feature Request

The impressive datashader python package (easier to install with conda) allows real-time visualisation of billions of rows of in memory pandas/numpy data (it uses numba JIT-ted optimised rasterisation routines), it's conceivable that it could be integrated with superset since superset nicely manages expensive query operations through celery tasks.

Here's a demonstration video of datashader https://www.youtube.com/watch?v=6m3CFbKmK_c

@xrmx
Copy link
Contributor

xrmx commented Feb 27, 2018

Superset does the visualization part in js on the client so not sure that datashader will fit in the picture.

@ariejdl
Copy link
Author

ariejdl commented Feb 27, 2018

If you were to consider it as a new back-end it would work, sending the front-end static renders, it's a big feature I'll admit, but for 2+ years from now you could find it very valuable, it would then compete with mapD https://www.mapd.com/demos/

@stale
Copy link

stale bot commented Apr 11, 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 11, 2019
@stale stale bot closed this as completed Apr 18, 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