Apache Superset Integration¶

Steps¶

Below are the steps to proceed:

Step1 : Navigate to the Data Product Hub¶

Start by accessing the Home Page of DataOS. From there, navigate to the Data Product Hub, where you can explore various Data Products available within the platform.

Step2: Browse and Select a Data Product:¶

In the Data Product Hub, browse through the list of Data Products. Click on the specific Data Product you wish to integrate with Superset. For example, select Sales360 from the list.

Step 3: Access Integration Options:¶

Navigate to the Access Options tab and scroll until you find the Superset option.

Step 4: Enter Connection Details:¶

Click on the Add Connection button. A connection window will open, prompting you to enter the necessary connection details.

Enter details of Host Address as given in the following syntax:

superset-<DATAOS_FQDN>

Replace <DATAOS_FQDN**> with the DataOS Fully Qualified Domain Name (FQDN). For example, if your context is "happy-raccoon" and the FQDN is happy-raccoon.dataos.app, then the correct entry would be:

superset-happy-raccoon.dataos.app

Enter Username and Password: The username and password for the Superset admin specific to the organization need to be provided. For example, in this case, you should add the credentials as adder_1 for both the username and password. This ensures proper access and management of Superset within the organizational context.

Click on Activate button. After clicking "Activate," a pop-up message will appear indicating that the sync has been completed.

Consuming the data model on Superset¶

Navigate to Superset, and the datasets will be created as shown below.

Click on any of the highlihted dataset to start creating visuals and dashboards.

Governance of model on Superset¶

When the Lens Model is activated via BI Sync on Superset, all user-level access controls and data policies from Lens are automatically applied to Superset.

The process is managed through authentication and authorization using your DataOS user ID and API key when accessing synced data models. This ensures that columns redacted by Lens data policies are restricted based on the user's group permissions.

For instance, if a user named iamgroot in the "Analyst" group is restricted from viewing the "Annual Salary" column, they will not see it either in the Data Product exploration page or Superset after syncing.