Skip to main content

Managed Apache Superset

Onehouse can deploy Apache Superset into your data plane, so your team can query your Lakegres Clusters from SQL Lab and build charts and dashboards on them. Superset runs inside your cloud account and your data never leaves your network.

In the Onehouse console, Superset lives under SERVE › SQL.

Beta Feature

This feature is in beta, and might not yet be available in your project.

Prerequisites​

  • A Lakegres Cluster without Lake Formation permissions. Each cluster you attach becomes a database in Superset. Clusters with Lake Formation permissions enforcement are not supported yet and are shown as Not supported.
  • An AWS project. Superset is not available on GCP or Azure projects yet.
  • For identity-provider sign-in: a Dataplane IDP connected in Account › Identity. Without one, you can still use basic sign-in.
  • You must be a project admin or an account admin to enable or change Superset.

Enable Superset​

  1. In the Onehouse console, open SERVE › SQL.
  2. Under Sign-in, choose how people sign in to Superset:
    • Identity provider (OIDC) (recommended): your team signs in with your identity provider through the project's Dataplane IDP, and each query runs as the signed-in user.
    • Basic sign-in: a single admin username and password managed in Superset. The admin creates everyone else's accounts in Superset, and queries run as a shared service account. Good for exploring.
  3. Under Query engines, select one or more Lakegres Clusters.
  4. Click Enable Superset. Deployment usually takes a few minutes. You can leave the page and come back.

When Superset is live, the page shows its Endpoint, the pinned Superset version, the attached clusters and the sign-in mode.

Open Superset​

Click Open Superset. Superset opens in a new tab.

Superset is exposed on an internal load balancer, so it is reachable only from your network. Follow these steps to connect to the internal load balancer.

With identity-provider sign-in, click Sign In with keycloak and sign in with your identity provider. Your email address becomes your Superset username.

Roles​

With identity-provider sign-in, Onehouse assigns Superset roles for you:

WhoSuperset roleCan
Project admins and account adminsAdminEverything, including SQL Lab, and creating and editing charts and dashboards
Everyone else who signs inReaderView dashboards and charts. No SQL Lab, and no creating or editing

Role changes in Onehouse reach Superset within about 15 minutes, and take effect the next time the user signs in to Superset.

Query identity and history​

With identity-provider sign-in, every query Superset sends to Lakegres runs as the signed-in user, not as a shared account. The query is recorded under that user's email in the Lakegres query history.

With basic sign-in, queries run as a shared service account, so they cannot be told apart by user.

Edit the configuration​

When Superset is live, click Edit configuration to:

  • Add or remove Lakegres Clusters. Removing a cluster breaks the charts, dashboards and saved queries that read from it.
  • Switch from basic sign-in to your identity provider. This is one-way: it cannot be switched back. Existing Superset users whose email matches their identity-provider email keep their dashboards and saved queries; anyone else gets a new, empty account.
  • Set a new basic admin password (basic sign-in only). Leave it empty to keep the current one.

Click Save changes. Superset is updated in place.

Disable or delete Superset​

Use the Danger zone on the SQL page:

  • Disable removes the Superset deployment but keeps dashboards, saved queries and users. Re-enabling restores them.
  • Delete permanently removes the deployment and all dashboards, saved queries and users. This cannot be undone.

If you delete a Lakegres Cluster that Superset uses, the console warns you first. The cluster is removed from Superset, and charts, dashboards and saved queries that read from it stop working.