Manage Superset assets

Operations on Superset assets (connections, dashboards, charts, datasets).

In general, these should be:

• Created in top-down order (connection, then dashboards, then charts and datasets)
• Deleted in bottom-up order (charts and datasets, then dashboards, then connections)¹

erDiagram
  Connection ||--o{ SupersetDashboard : contains
  SupersetDashboard ||--o{ SupersetChart : contains
  SupersetDashboard ||--o{ SupersetDataset : contains

Asset structure

Connection

2.0.0 1.0.0

A Superset connection requires a name and qualifiedName. For creation, specific settings are also required to distinguish it as a Superset connection rather than another type of connection. In addition, at least one of adminRoles, adminGroups, or adminUsers must be provided.

Java Python Raw REST API

String adminRoleGuid = RoleCache.getIdForName("$admin"); // (1)
Connection connection = Connection.creator( // (2)
        "superset-connection", // (3)
        AtlanConnectorType.SUPERSET, // (4)
        List.of(adminRoleGuid), // (5)
        List.of("group2"), // (6)
        List.of("jsmith")) // (7)
    .build();
AssetMutationResponse response = connection.save(); // (8)
String connectionQualifiedName = response.getCreatedAssets().get(0).getQualifiedName(); // (9)

1. Retrieve the GUID for the admin role, to use later for defining the roles that can administer the connection.
2. Build up the minimum request to create a connection.
3. Provide a human-readable name for your connection, such as production or development.
4. Set the type of connection to Superset.
5. List the workspace roles that should be able to administer the connection (or null if none). All users with that workspace role (current and future) will be administrators of the connection. Note that the values here need to be the GUID(s) of the workspace role(s). At least one of adminRoles, adminGroups, or adminUsers must be provided.
6. List the group names that can administer this connection (or null if none). All users within that group (current and future) will be administrators of the connection. Note that the values here are the name(s) of the group(s). At least one of adminRoles, adminGroups, or adminUsers must be provided.
7. List the user names that can administer this connection (or null if none). Note that the values here are the username(s) of the user(s). At least one of adminRoles, adminGroups, or adminUsers must be provided.
8. Actually call Atlan to create the connection.
9. Retrieve the qualifiedName for use in subsequent creation calls. (You'd probably want to do some null checking first.)

from pyatlan.cache.role_cache import RoleCache
from pyatlan.client.atlan import AtlanClient
from pyatlan.model.assets import Connection, SupersetDashboard, SupersetChart, SupersetDataset
from pyatlan.model.enums import AtlanConnectorType

admin_role_guid = RoleCache.get_id_for_name("$admin") # (1)
connection = Connection.creator( # (2)
  name = "superset-connection", # (3)
  connector_type = AtlanConnectorType.SUPERSET, # (4)
  admin_roles = [admin_role_guid], # (5)
  admin_groups = ["group2"], # (6)
  admin_users = ["jsmith"] # (7)
)

response = client.asset.save(connection) # (8)
connection_qualified_name = response.assets_created(asset_type=Connection)[0].qualified_name # (9)

1. Retrieve the GUID for the admin role, to use later for defining the roles that can administer the connection.
2. Build up the minimum request to create a connection.
3. Provide a human-readable name for your connection, such as production or development.
4. Set the type of connection to Superset.
5. List the workspace roles that should be able to administer the connection (or None if none). All users with that workspace role (current and future) will be administrators of the connection. Note that the values here need to be the GUID(s) of the workspace role(s). At least one of admin_roles, admin_groups, or admin_users must be provided.
6. List the group names that can administer this connection (or None if none). All users within that group (current and future) will be administrators of the connection. Note that the values here are the name(s) of the group(s). At least one of admin_roles, admin_groups, or admin_users must be provided.
7. List the user names that can administer this connection (or None if none). Note that the values here are the username(s) of the user(s). At least one of admin_roles, admin_groups, or admin_users must be provided.
8. Actually call Atlan to create the connection.
9. Retrieve the qualified_name for use in subsequent creation calls. (You'd probably want to do some null checking first.)

{
  "entities": [
    {
      "typeName": "Connection", // (1)
      "attributes": {
        "name": "superset-connection", // (2)
        "connectorName": "superset", // (3)
        "qualifiedName": "default/superset/123456789", // (4)
        "category": "bi", // (5)
        "adminRoles": [ // (6)
          "e7ae0295-c60a-469a-bd2c-fb903943aa02"
        ],
        "adminGroups": [ // (7)
          "group2"
        ],
        "adminUsers": [ // (8)
          "jsmith"
        ]
      }
    }
  ]
}

1. The typeName must be exactly Connection.
2. Human-readable name for your connection, such as production or development.
3. The connectorName must be exactly superset.
4. The qualifiedName should follow the pattern: default/superset/<epoch>, where <epoch> is the time in milliseconds at which the connection is being created.
5. The category must be bi.
6. List any workspace roles that can administer this connection. All users with that workspace role (current and future) will be administrators of the connection. Note that the values here need to be the GUID(s) of the workspace role(s). At least one of adminRoles, adminGroups, or adminUsers must be provided.
7. List any groups that can administer this connection. All users within that group (current and future) will be administrators of the connection. Note that the values here are the name(s) of the group(s). At least one of adminRoles, adminGroups, or adminUsers must be provided.
8. List any users that can administer this connection. Note that the values here are the username(s) of the user(s). At least one of adminRoles, adminGroups, or adminUsers must be provided.

Access policies

Atlan creates the policies that grant access to a connection, including the ability to retrieve the connection and to create assets within it, asynchronously. It can take several seconds (even up to approximately 30 seconds) before these are in place after creating the connection.

You may therefore need to wait before you'll be able to create the assets below within the connection.

To confirm access, retrieve the connection after it has been created. The SDKs' retry loops will automatically retry until the connection can be successfully retrieved. At that point, your API token has permission to create the other assets.

Note: if you are reusing an existing connection rather than creating one via your API token, you must give your API token a persona that has access to that connection. Otherwise all attempts to create, read, update, or delete assets within that connection will fail due to a lack of permissions.

SupersetDashboard

2.2.3 1.12.8

A Superset dashboard requires a name and a qualifiedName. For creation, you also need to specify the connectionQualifiedName of the connection for the dashboard.

Java Python Raw REST API

SupersetDashboard dashboard = SupersetDashboard.creator( // (1)
        "ss-dashboard", // (2)
        connectionQualifiedName) // (3)
    .build();
AssetMutationResponse response = dashboard.save(); // (4)
dashboard = response.getResult(dashboard); // (5)

1. Build up the minimum request to create a dashboard.
2. Provide a human-readable name for your dashboard.
3. Provide the qualifiedName of the connection for this dashboard.
4. Actually call Atlan to create the dashboard.
5. Retrieve the created dashboard for use in subsequent creation calls. (You'd probably want to do some null checking first.)

dashboard = SupersetDashboard.creator( # (1)
  name = "ss-dashboard", # (2)
  connection_qualified_name = connection_qualified_name # (3)
)
response = client.asset.save(dashboard) # (4)
superset_dashboard_qualified_name = response.assets_created(asset_type=SupersetDashboard)[0].qualified_name # (5)

1. Build up the minimum request to create a dashboard.
2. Provide a human-readable name for your dashboard.
3. Provide the qualified_name of the Superset connection for this dashboard.
4. Actually call Atlan to create the dashboard.
5. Retrieve the created dashboard for use in subsequent creation calls. (You'd probably want to do some null checking first.)

{
  "entities": [
    {
      "typeName": "SupersetDashboard", // (1)
      "attributes": {
        "name": "ss-dashboard", // (2)
        "qualifiedName": "default/superset/123456789/ss-dashboard", // (3)
        "connectionQualifiedName": "default/superset/123456789", // (4)
        "connectorName": "superset" // (5)
      }
    }
  ]
}

1. The typeName must be exactly SupersetDashboard.
2. Human-readable name for your dashboard.
3. The qualifiedName should follow the pattern: default/superset/<epoch>/<dashboard_name>, where default/superset/<epoch> is the qualifiedName of the connection for this dashboard and <dashboard_name> is the name for this dashboard.
4. The connectionQualifiedName must be the exact qualifiedName of the connection for this dashboard.
5. The connectorName must be exactly superset.

SupersetChart

2.2.3 1.12.8

A Superset chart requires a name and a qualifiedName. For creation, you also need to specify the connectionQualifiedName of the connection for the chart, and the names and qualifiedNames of the chart's ancestors.

Java Python Raw REST API

SupersetChart chart = SupersetChart.creator( // (1)
        "ss-chart", // (2)
        dashboard) // (3)
    .build();
AssetMutationResponse response = chart.save(); // (4)

1. Build up the minimum request to create a chart.
2. Provide a human-readable name for your chart.
3. Provide the dashboard for this chart.
4. Actually call Atlan to create the chart.

chart = SupersetChart.creator( # (1)
  name = "ss-chart ", # (2)
  superset_dashboard_qualified_name = superset_dashboard_qualified_name, # (3)
  connection_qualified_name = connection_qualified_name # (4)
)
response = client.asset.save(chart) # (5)

1. Build up the minimum request to create a chart.
2. Provide a human-readable name for your chart.
3. Provide the qualified_name of the dashboard.
4. Optional, provide the qualified_name of the connection for the chart.
5. Actually call Atlan to create the chart.

{
  "entities": [
    {
      "typeName": "SupersetChart", // (1)
      "attributes": {
        "name": "ss-chart", // (2)
        "qualifiedName": "default/superset/123456789/ss-dashboard/ss-chart", // (3)
        "connectionQualifiedName": "default/superset/123456789", // (4)
        "connectorName": "superset", // (5)
        "SupersetDashboard": { // (6)
          "typeName": "SupersetDashboard", // (7)
          "uniqueAttributes": { // (8)
            "qualifiedName": "default/superset/123456789/ss-dashboard"
          }
        },
        "supersetDashboardQualifiedName": "default/superset/123456789/ss-dashboard" // (9)
      }
    }
  ]
}

1. The typeName must be exactly SupersetChart.
2. Human-readable name for your chart.
3. The qualifiedName should follow the pattern: default/superset/<epoch>/<dashboard_name>/<chart_name>, where default/superset/<epoch>/<dashboard_name> is the qualifiedName of the dashboard for this chart and <chart_name> is the name for this chart.
4. The connectionQualifiedName must be the exact qualifiedName of the connection for this chart.
5. The connectorName must be exactly superset.
6. The dashboard in which this chart exists is embedded in the SupersetDashboard attribute.
7. The typeName for this embedded reference must be SupersetDashboard.
8. To complete the reference, you must include a uniqueAttributes object with the qualifiedName of the dashboard. Note: the dashboard must already exist in Atlan before creating the chart.
9. The supersetDashboardQualifiedName should be the qualifiedName of the dashboard.

SupersetDataset

2.2.3 1.12.8

A Superset dataset requires a name and a qualifiedName. For creation, you also need to specify the connectionQualifiedName of the connection for the dataset, and the names and qualifiedNames of the dataset's ancestors.

Java Python Raw REST API

SupersetDataset dataset = SupersetDataset.creator( // (1)
        "ss-dataset", // (2)
        dashboard) // (3)
    .build();
AssetMutationResponse response = dataset.save(); // (4)

1. Build up the minimum request to create a dataset.
2. Provide a human-readable name for your dataset.
3. Provide the dashboard for this dataset.
4. Actually call Atlan to create the dataset.

dataset = SupersetDataset.creator( # (1)
  name = "ss-dataset ", # (2)
  superset_dashboard_qualified_name = superset_dashboard_qualified_name, # (3)
  connection_qualified_name = connection_qualified_name # (4)
)
response = client.asset.save(dataset) # (5)

1. Build up the minimum request to create a dataset.
2. Provide a human-readable name for your dataset.
3. Provide the qualified_name of the dashboard.
4. Optional, provide the qualified_name of the connection for the dataset.
5. Actually call Atlan to create the dataset.

{
  "entities": [
    {
      "typeName": "SupersetDataset", // (1)
      "attributes": {
        "name": "ss-dataset", // (2)
        "qualifiedName": "default/superset/123456789/ss-dashboard/ss-dataset", // (3)
        "connectionQualifiedName": "default/superset/123456789", // (4)
        "connectorName": "superset", // (5)
        "SupersetDashboard": { // (6)
          "typeName": "SupersetDashboard", // (7)
          "uniqueAttributes": { // (8)
            "qualifiedName": "default/superset/123456789/ss-dashboard"
          }
        },
        "supersetDashboardQualifiedName": "default/superset/123456789/ss-dashboard" // (9)
      }
    }
  ]
}

1. The typeName must be exactly SupersetDataset.
2. Human-readable name for your dataset.
3. The qualifiedName should follow the pattern: default/superset/<epoch>/<dashboard_name>/<dataset_name>, where default/superset/<epoch>/<dashboard_name> is the qualifiedName of the dashboard for this dataset and <dataset_name> is the name for this dataset.
4. The connectionQualifiedName must be the exact qualifiedName of the connection for this dataset.
5. The connectorName must be exactly superset.
6. The dashboard in which this dataset exists is embedded in the SupersetDashboard attribute.
7. The typeName for this embedded reference must be SupersetDashboard.
8. To complete the reference, you must include a uniqueAttributes object with the qualifiedName of the dashboard. Note: the dashboard must already exist in Atlan before creating the dataset.
9. The supersetDashboardQualifiedName should be the qualifiedName of the dashboard.

Available relationships

Every level of the business intelligence structure is an Asset, and can therefore be related to the following other assets.

erDiagram
  Asset }o--o{ AtlasGlossaryTerm : meanings
  Asset ||--o{ Link : links
  Asset ||--o| Readme : readme
  Asset }o--o{ Process : inputToProcesses
  Asset }o--o{ Process : outputFromProcesses

AtlasGlossaryTerm

A glossary term provides meaning to an asset. The link terms to assets snippet provides more detail on setting this relationship.

Link

A link provides additional context to an asset, by providing a URL to additional information.

Readme

A README provides rich documentation for an asset. The add asset READMEs snippet provides more detail on setting this relationship.

Process

A process provides lineage information for an asset. An asset can be both an input and an output for one or more processes. The lineage snippets provide more detail on creating and working with lineage.

---

1. Although if you want to delete everything in a connection, your better avenue is the packaged connection delete utility in the UI. ↩

---