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

What's the relationship between superset-ui and apache/incubator-superset? #170

Open
syang opened this issue Jun 12, 2019 · 5 comments

Comments

Projects
None yet
3 participants
@syang
Copy link

commented Jun 12, 2019

  • What's the relationship between apache-superset/superset-ui and apache/incubator-superset? Is there a place talking about this, or can someone give a high level overview?

  • What's the relationship between apache-superset/superset-ui and https://github.com/apache-superset/superset-ui-plugins?

If someone can give a high level architecture overview, that would be great.

@issue-label-bot issue-label-bot bot added the #question label Jun 12, 2019

@issue-label-bot

This comment has been minimized.

Copy link

commented Jun 12, 2019

Issue-Label Bot is automatically applying the label #question to this issue, with a confidence of 0.98. Please mark this comment with 👍 or 👎 to give our bot feedback!

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

@kristw

This comment has been minimized.

Copy link
Contributor

commented Jun 12, 2019

What's the relationship between apache-superset/superset-ui and apache/incubator-superset? Is there a place talking about this, or can someone give a high level overview?

Reusable components and fundamental utilities from incubator-superset are extracted and/or rewritten in @superset-ui, such as number formatting, ajax calls. @superset-ui also provides base classes for plugins.

What's the relationship between apache-superset/superset-ui and https://github.com/apache-superset/superset-ui-plugins?

Most of the visualizations previously in incubator-superset are refactored into plugins and removed from incubator-superset. This is because the collection of visualizations has grown organically over time, with varying level of qualities. Making everything plugins so all deployments of Superset can include only what the organizations need. It also open up the possibilities for everyone to develop specialized/experimental plugins in their own repo/space without polluting the entire project. The @superset-ui-plugins uses base classes from @superset-ui.

@syang

This comment has been minimized.

Copy link
Author

commented Jun 12, 2019

Thanks to Kris.

To give some more color why I asked the above question. Here is our thoughts to explore when looking at if Superset is a good fit or not:

  • We have an internal React web app allowing employees to do other data processing work;

  • We are interested in embedding Superset as our BI work console along with the above app (so that our data analysts can work in front of the integrated Web App)

By quickly glimpsing through the code, I felt the original Superset product is a Flask app with a lot of server side rendered templates as presentation layer (is that true understanding?). And sounds like apache-superset/superset-ui is meant to separate the presentation layer out of the server side project?

Thanks

@kristw

This comment has been minimized.

Copy link
Contributor

commented Jun 13, 2019

Some of the presentation layer, mostly charts. There are still too many things coupling with the flask app that are harder to separate.

@mistercrunch

This comment has been minimized.

Copy link
Contributor

commented Jun 14, 2019

@syang Superset is mostly React at this point with leftover MVC scaffolding in some areas (mostly the CRUD views). We're slowly chiseling at what is left of the MVC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.