Skip to content

Instantly share code, notes, and snippets.

@michael-erasmus

michael-erasmus/README.md

Created June 5, 2018 19:44
Show Gist options
  • Save michael-erasmus/570a02e14464ce5f9ed48682fb12fd4f to your computer and use it in GitHub Desktop.
Save michael-erasmus/570a02e14464ce5f9ed48682fb12fd4f to your computer and use it in GitHub Desktop.
Download ZIP
Playing around with Apache Superset
Raw
README.md

Watched this video: https://www.youtube.com/watch?v=W_Sp4jo1ACg

Installed Superset locallly using these instructions, slightly tweaked for use with pipenv.

cd ~/learn
mkdir superset
cd superset
pipenv --three
pipenv install superset
pipenv shell
fabmanager create-admin --app superset
superset db upgrade
superset load_examples #this took a little while to finish
superset init
superset runserver -d

What I like about Superset:

  • It's open source.
  • It's built in Python and uses Flask.
  • It uses d3 and supports pretty nice set of visualizations, with interesting interactivity.
  • It seems to have a pretty nice SQL editor (SqlLab), which seems to be the primary way to model data.

What's different about Superset (mostly compared to Looker)

  • It seems to lack some of the 'workflow' features Looker has, like scheduled Looks, public Looks, link shortening, etc
  • It has nothing like LookML (data is mostly modelled with SQL, but can be annotated with custom measures/dimension)
  • Explore views are quite different from how Looker would do it (much more focused on how you wanted to display/visualize data, with different UI's for each visualization type)
  • In general it seems like superset tries less to 'shield' users from the underlying SQL entities
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment