# Add a Hive Native Datastore with a New Connection

Source: https://userguide.qualytics.io/source-datastore/datastore/native/hive/how-tos/add-new-connection/

This page walks you through adding a **Hive Native** source datastore while creating its connection: every field the form asks for, section by section, followed by the steps to test and finish.

Once the datastore is created, run a Sync to discover the tables in the selected database. Tables that Hive Native declines to read, such as views and transactional tables, are reported individually while the rest of the database syncs normally.

> **Tip: Already have a connection?**
>
> To add a Hive Native datastore on a connection that already exists, go to [Add with an Existing Connection](https://userguide.qualytics.io/source-datastore/datastore/native/hive/how-tos/add-existing-connection/).

Before you start, review the [Hive Native Permissions](https://userguide.qualytics.io/source-datastore/datastore/native/hive/deep-dive/permissions/) and the [Authentication](https://userguide.qualytics.io/source-datastore/datastore/native/hive/deep-dive/authentication/) page. Reaching the metastore is not enough on its own: the connection also needs to reach the storage the metastore points at.

> **Warning**
>
> Hive 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](https://userguide.qualytics.io/source-datastore/enrichment-datastore/how-tos/link-during-creation/) or [afterwards](https://userguide.qualytics.io/source-datastore/enrichment-datastore/how-tos/link-enrichment/).

## Field reference

After you choose **New Connection**, the form shows three sections. **Connection Properties** holds everything that belongs to the connection, including the **Secrets Management** and **Authentication** groups inside it. **Location** holds the database to monitor, and **General** holds the datastore's own settings.

### Connection Properties

These fields define the metastore Qualytics connects to. They belong to the connection, so they can be reused by other datastores later. **Secrets Management** and **Authentication**, described next, sit inside this section.

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Connection Name** | Yes | Text | A label for the saved connection (e.g., `acme_hive_metastore`), so other datastores can reuse it later. |
| **Metastore URI** | Yes | Text | The address of the Hive metastore, in the form `thrift://metastore-host:9083`. For a highly available metastore, list each address separated by commas. |
| **Warehouse Directory** | No | Text | The warehouse root, for example `/user/hive/warehouse`. Optional, and not needed for reading: Qualytics takes each table's location from the metastore rather than from a warehouse root. |

> **Note: No Catalog field**
>
> Connectors such as Athena ask for a **Catalog**, the level above the database. Hive has no such level, only databases and tables, so the form does not ask for one. Qualytics works the rest out from the metastore address.

### Authentication

Shown inside **Connection Properties**. Hive Native authenticates with Kerberos. See [Hive Native Authentication](https://userguide.qualytics.io/source-datastore/datastore/native/hive/deep-dive/authentication/) for which identity belongs in which field.

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Type** | No | Option | **Kerberos**, the only available option and the default. The metastore protocol has no user and password authentication of its own. |
| **Client Principal** | Yes | Text | The login identity in the keytab, for example `qualytics@EXAMPLE.COM`. Do not use `_HOST`. |
| **Metastore Service Principal** | No | Text | The metastore's service identity, for example `hive/_HOST@EXAMPLE.COM`. Defaults to `hive/_HOST@` followed by the Kerberos login realm. Set it explicitly for a different service name or realm. |
| **Keytab** | No | File | The keytab holding the key for the identity Qualytics should present. Must be named with a `.keytab` extension. Stored encrypted and never displayed back. Upload it on every connection: an empty field works only on an older self-hosted deployment with a Kerberos login of its own. Or click **Type a value instead**  and enter a `${key}` reference to the file held in your secrets manager, stored as its base64 form. See [File fields](https://userguide.qualytics.io/source-datastore/datastore/connection/hashicorp-vault/deep-dive/how-it-works/#file-fields). |
| **krb5.conf** | No | File | The Kerberos configuration for the cluster's realm, so Qualytics can reach its Key Distribution Center. Upload it with the keytab. An empty field falls back to the deployment's own Kerberos configuration, which only older self-hosted deployments have. Or click **Type a value instead**  and enter a `${key}` reference to the file held in your secrets manager. See [File fields](https://userguide.qualytics.io/source-datastore/datastore/connection/hashicorp-vault/deep-dive/how-it-works/#file-fields). |
| **RPC Protection** | No | Option | **Authentication only**, **Integrity (signed)**, or **Privacy (encrypted)**. Must match the metastore's protection level. Leave it empty for **Authentication only**. See [RPC protection](https://userguide.qualytics.io/source-datastore/datastore/native/hive/deep-dive/authentication/#rpc-protection). |
| **hdfs-site.xml** | No | File | The cluster's HDFS client configuration. Required when table locations use a highly available nameservice. See [HDFS client configuration](https://userguide.qualytics.io/source-datastore/datastore/native/hive/deep-dive/authentication/#hdfs-client-configuration). |

If **Keytab** is left empty, the connection test fails unless your deployment has a Kerberos login of its own, which self-hosted deployments on Helm chart 2026.9.1 or later do not. See [Connections without a keytab](https://userguide.qualytics.io/source-datastore/datastore/native/hive/deep-dive/authentication/#connections-without-a-keytab) for what to enter in that case.

### Secrets Management

Also inside **Connection Properties**, and optional. Use it only if you want Qualytics to pull credentials from a secrets manager instead of typing them into the form. Turn on **HashiCorp Vault** to show the fields below. Despite the label, any secrets manager that exposes a compatible REST API works; see [HashiCorp Vault](https://userguide.qualytics.io/source-datastore/datastore/connection/hashicorp-vault/deep-dive/introduction/).

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Login URL** | Yes | Text | The full URL of the login endpoint (e.g., `https://vault.example.com/v1/auth/approle/login`). With Vault namespaces, add the namespace after `/v1/`, as in `/v1/<namespace>/auth/approle/login`. |
| **Credentials Payload** | Yes | Text | A JSON body containing the credentials Vault expects (e.g., `{"role_id":"...","secret_id":"..."}`). |
| **Token JSONPath** | Yes | Text | The JSONPath that extracts the client token from Vault's response. Defaults to `$.auth.client_token`. |
| **Secret URL** | Yes | Text | The full URL of the secret, including `https://` and the host (e.g., `https://vault.example.com/v1/secret/data/hive`). With Vault namespaces, add the namespace after `/v1/`. |
| **Token Header Name** | Yes | Text | The HTTP header name used to send the token. Defaults to `X-Vault-Token`. |
| **Data JSONPath** | Yes | Text | The JSONPath that extracts the key/value pairs from Vault's response. Use `$.data.data` for a KV version 2 secret (its API path contains `/data/`) and `$.data` for KV version 1 or the database secrets engine. The form pre-fills `$.data`. |

> **Note**
>
> Reference a key from the secret in any **Connection Properties** or **Authentication** field with `${key}`, for example `${password}`. Write it with braces (`${key}`, never `$.key`) and match the key name's case. Qualytics resolves it each time the connection is opened, so a changed value takes effect on the next connection. Setup steps, the namespace rule, and a troubleshooting page are on the [HashiCorp Vault](https://userguide.qualytics.io/source-datastore/datastore/connection/hashicorp-vault/deep-dive/introduction/) pages.

### Location

Pick the Hive database 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 |
| --- | --- | --- | --- |
| **Database** | Yes | Option | One or more Hive databases to monitor. The dropdown is filled in once Qualytics connects to the metastore. Each database you pick becomes its own Qualytics datastore. |

### General

The datastore's own settings.

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Name** | Yes | Text | The datastore name in Qualytics. Comes suggested from the connection name and the database, so you can leave it blank to accept that suggestion. |
| **Group** | No | 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** | Yes | Option | Select one or more teams to associate with this source datastore. |
| **Initiate Sync** | No | 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. |

> **Note: Selecting more than one database**
>
> When you pick several databases 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 database name: `hive_{{schema}}` becomes `hive_sales`, `hive_finance`, and so on. Left empty, each datastore is named from the connection name and its database.

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; see [Permissions](https://userguide.qualytics.io/source-datastore/datastore/native/hive/deep-dive/permissions/) for the ports 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 **New Connection** next to the **Search**  field.

**Step 5**: Select **Hive Native** from the connector grid. Use the search field to filter connectors by name.

**Step 6**: Fill in the fields of **Connection Properties**, **Authentication**, **Location**, and **General**, as described in the [Field reference](https://userguide.qualytics.io/source-datastore/datastore/native/hive/how-tos/add-new-connection/#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 you change a connection field after a successful test, test again. If the test fails, see [Troubleshooting](https://userguide.qualytics.io/source-datastore/datastore/native/hive/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](https://userguide.qualytics.io/source-datastore/enrichment-datastore/how-tos/link-during-creation/).

**Step 9**: A success dialog confirms that your datastore has been added. Click **Go to your datastore** to open its page.

*Last updated: November 12, 2026.*
