ODA User Guide
Connected Systems
How connected systems work in ODA Data Studio, including supported types, connector-specific authoring behavior, and practical guidance.
In Data Studio, connected systems are account integrations configured through secrets and available to select on the project canvas. When you click Add a system, the picker shows enabled connections and their types.
After selecting a connected system, add one or more sources beneath it. Those sources use the selected connection as they move through ingestion and transformation steps.
How Connected Systems Are Resolved
When you start source setup from a selected system, Data Studio presents the connection-specific options for that type.
If a connection type is not supported for source setup, Data Studio displays a message and prevents configuration until you select a supported type.
Supported Connected System Types
These secret types are currently supported for source setup:
azure data lakepostgressnowflaketds(SQL Server)azure event hubaws s3delta sharing
These are the types that can currently drive the source-add experience through registered handlers in Data Studio.
Connector-Specific Authoring Behavior
Connected systems are not a single generic form in ODA. Each supported type provides connector-specific UX and checks. For example:
- Delta Sharing presents guided selection for
share -> schema -> table, supports previewing files and estimated row counts, allows selecting specific files, and can fetch/refresh schema before save. - Postgres exposes database/schema/query inputs and includes a built-in Test action so users can validate connectivity and query execution before saving the source.
This connector-aware behavior helps reduce misconfiguration by checking required fields before a source is saved.
Practical Guidance for Users
- Create and maintain the required account secret first, then use it as a connected system in Data Studio.
- Choose a connected system whose secret type matches a supported source handler.
- Use connector-specific test/preview actions (where available) before saving.
- If you see an unsupported secret-type message, switch to a supported secret type or ask an administrator to provision the correct integration secret.
Troubleshooting Adding a System
- Supported types and availability: the Select a system picker only lists enabled secrets whose type is one of seven supported data-source types—Azure Data Lake, Azure Event Hub, AWS S3, Postgres, Snowflake, TDS (SQL Server), and Delta Sharing. Secrets of any other type (for example Azure Active Directory, Microsoft App Logic, Azure Logic App, AMQP, or a Databricks-type secret) still appear in Settings > Secrets, but not in the picker.
- Enabled secrets may not appear in the picker: the Status column on the Settings > Secrets list only reflects each secret's own Enabled/Disabled toggle. A secret showing "Enabled" is not guaranteed to appear as a System—it must also be one of the supported types above. Check the secret's Type column when a connection is missing.
- Databricks and Databricks SQL are not listed as supported secret types for the project System picker: Databricks credentials are only used by Labs (Catalog Registration and Zone to Device Registry) and are never offered as a pipeline System, even though they are visible and configurable like any other secret under Settings > Secrets.
Adding a Data Lake System
An Azure Data Lake (ADLS) connection is often called a Storage Account System, since its secret authenticates directly against an Azure Storage Account. Unlike Postgres, adding an ADLS source browses real containers and folders instead of asking you to type a database/schema/query.
Storage Account System
- Create the secret first if one doesn't exist: in Settings > Secrets, choose Create secret, name it, and select Azure Data Lake as the type. On its detail page, fill in the three required Values—
account_name,account_key, andcontainer—then save (see Create a Connected System for the general flow). - In the project's Select a system panel, click the Azure Data Lake connection. Optra opens the Add ADLS Sources panel (plural—this panel supports adding several sources from the same storage account in one session) and lists every container in that storage account, fetched live using the secret's
account_name/account_key. - Click a container row to expand it; Optra loads and lists its top-level folders and files. Click a folder to expand it further and load its children the same way.
- Hover a file or folder row to reveal an Add button, then click it to add that item as a source immediately—there is no separate Save or Test step like Postgres. The added row turns green with a check mark, and the panel footer's counter increases.
- Repeat for as many files/folders as you need; each becomes its own Source node on the canvas (flash message "ADLS source added successfully."), connected to this same ADLS system node.