Add a Unity Catalog Native Datastore with an Existing Connection
This page walks you through adding a Unity Catalog Native source datastore on a connection you already saved: what comes already filled in, the two sections left for you to complete, and the steps to test and finish. For what a connection is and why reusing one matters, see Reusing a Connection.
Once the datastore is created, run a Sync to discover the tables in the selected schema. Objects that Unity Catalog Native cannot read, such as views, do not become containers: the Sync's warning says how many were skipped, and names any table the catalog listed but Qualytics could not read. The rest of the schema syncs normally.
No connection yet?
If this is your first Unity Catalog Native datastore, create the connection first in Add with a New Connection.
Warning
Unity Catalog Native cannot be used as an enrichment datastore. After you add it as a source, link a separate enrichment datastore as its destination to store anomalies and metadata: either during creation or afterwards.
What comes already filled in
When you select a saved Unity Catalog Native connection, the Connection Properties, Authentication, and Secrets Management sections come already filled in and read-only. Qualytics has already validated those credentials, so there is nothing to type there:
| Section | Fields | Why Read-Only |
|---|---|---|
| Connection Properties | Connection Name, URL, Catalog | They identify the catalog the saved connection points at. A connection monitors one catalog, so the new datastore reads from the same one. |
| Authentication | Type, Access Token or Client ID, Client Secret, Token Endpoint | The credentials were validated when the connection was saved. The token and the secret are never displayed back. The field shows only that a value is stored. |
| Secrets Management | Vault fields, when the connection uses them | Configured once on the connection. |
Edits apply to every datastore on the connection
To change a saved connection's credentials, edit the connection through Manage Connections. Edits there apply to every datastore that reuses the connection, not only the one you are creating.
Start a new connection from this one
To use the selected connection as a starting point for a brand-new one instead, for example to monitor a different catalog with the same credential, click the Duplicate as a new connection button on it. The form switches to the new-connection mode with the URL, the catalog, and the authentication type already filled in for you to adjust, as described in Add with a New Connection. The access token or client secret is not copied, so enter it again.
Field reference
Location and General are the only two sections left for you to fill in.
Location
Pick the schema Qualytics should read from. Unlike Connection Properties, this section belongs to the datastore rather than to the connection, so it is filled in on both flows.
| Field | Required | Type | Description |
|---|---|---|---|
| Schema | Option | One or more schemas of the connection's catalog to monitor. The dropdown lists the schemas that the saved credential can see, and you can also type a name. Each schema you pick becomes its own Qualytics datastore. |
General
The datastore's own settings.
| Field | Required | Type | Description |
|---|---|---|---|
| Name | Text | The datastore name in Qualytics. Comes suggested from the connection name and the schema, so you can leave it blank to accept that suggestion. | |
| Group | Option | Organizes your datastores under a shared group in the navigation tree. Select an existing group, or turn on Add New Group to create one. | |
| Teams | Option | Select one or more teams to associate with this source datastore. | |
| Initiate Sync | Checkbox | Ask Qualytics to run the first Sync for you once the datastore is created. You can always run a Sync yourself from the datastore afterwards. |
Selecting more than one schema
When you pick several schemas in Location, each one becomes its own datastore and Name is replaced by Name Template, a naming pattern applied to all of them. Use {{schema}} as the placeholder for the schema name: prod_{{schema}} becomes prod_sales, prod_finance, and so on. Left empty, each datastore is named from the connection name and its schema.
Below the form, an information banner lists the Public addresses and Private addresses your datastore connections originate from. Allow the ones that match your network setup through your security groups or firewall rules, on the catalog side and on the storage side. See Permissions for the services involved.
Steps
Step 1: Navigate to the Datastores page.
Step 2: Click the Add button at the top-right corner and choose Source from its menu.
Step 3: The Datastore step opens, the first of two.
Step 4: Select Existing Connection next to the Search field.
Step 5: Select the saved Unity Catalog Native connection from the grid. Use the search field to filter connections by name. The Connection Properties, Authentication, and Secrets Management sections come already filled in and read-only.
Step 6: Fill in the fields of Location and General, as described in the Field reference.
Step 7: Click Test connection. A success message confirms that the connection has been verified.
Info
The Finish and Next buttons stay disabled until the connection test passes on the current values. If the test fails, see Troubleshooting.
Step 8: Click Finish to create the datastore.
Tip
To link an enrichment destination so Qualytics can store anomalies and metadata from the first operation, click Next instead of Finish. See Link Enrichment on Datastore Creation.
Step 9: A success dialog confirms that your datastore has been added. Click Go to your datastore to open its page.