Semantic Layer Sync with Apache Superset

Configuration

To create a new sync, choose Apache Superset:

Data model is synchronized via Superset API which uses a user name and a password for authentication. You can use your own user name and password or create a new service account. You can copy a url at any page of your Superset workspace.

If your Superset instance is served with a certificate from a private or internal CA, the sync fails at the connection step with a SELF_SIGNED_CERT_IN_CHAIN / “self-signed certificate in certificate chain” error. Commit the CA certificate (PEM) to your data model’s Git repository, e.g., as certs/my-ca.pem, and set the NODE_EXTRA_CA_CERTS environment variable to its absolute path, e.g., /cube/conf/certs/my-ca.pem — the sync’s outbound requests run in Node.js, so this is what makes it trust the certificate.

Example confguration for Superset:

from cube import config

@config('semantic_layer_sync')
def semantic_layer_sync(ctx: dict) -> list[dict]:
  return [
    {
      'type': 'superset',
      'name': 'Superset Sync',
      'config': {
        'user': 'mail@example.com',
        'password': '4dceae-606a03-93ae6dc7',
        'url': 'superset.example.com',
        'database': 'Cube: production-deployment'
      }
    }
  ]

module.exports = {
  semanticLayerSync: ({ securityContext }) => {
    return [
      {
        type: "superset",
        name: "Superset Sync",
        config: {
          user: "mail@example.com",
          password: "4dceae-606a03-93ae6dc7",
          url: "superset.example.com",
          database: "Cube: production-deployment"
        }
      }
    ]
  }
}

Getting Started

Explore & Analyze

Present & Share

Organize content

Data Modeling

Pre-aggregations

Integrations

Semantic Layer Sync with Apache Superset

Configuration

​Configuration

Configuration